apache not starting

[farfields]

I've been writing a small webpage runing from the N2100, which seems to work fine.

I have attempted to write an SSL certificate following the instructions at:
www.onbeat.dk/thecus/index.php/N2100_Fixing_Certificate_problems

BUT. Apache is not restarting. I get error message:
no listening sockets available, shutting down
Unable to open logs

rebooting the box makes no difference.

I have RAID access, my webpage runs, but the Thecus https access is not functioning.

Is this caused by a fault in the httpd? I'm out of my depth with this now and would appreciate some advice on recovery.

If there are particular files at fault, can I correct, or replace these?

thanks in advance.

[dbridges]

At a guess I would say that the port is already in use.

Simple answer: Try changing the port number of your web page.

Complex answer:
I expect that your attempt to write a SSL certificate is not related to this problem.

Are you running your website within the default apache that the thecus uses? Or have you tried to install another one?

How have you changed the thecus apache configuration?

Did you just add your site as a virtual host or an aliased directory (or both).

Have you changed httpd.conf or ssl.conf or both?

What listen commands do you have in place in these files?

The default should be a single
Listen 0.0.0.0:80 in httpd.conf
and
Listen 0.0.0.0:443 in ssl.conf

If you're running a virtual host of another port then you'll need to add that one as well but make sure that it's free. port 1080 is usually a safe choice.

You say that the thecus https (ssl) is not working. I'm assuming that the http is working. That would indicate that you've broken something in the ssl.conf

Did you edit this to get your website into ssl at the same time that you tried the certificate change?

Did you get your site working under the existing SSL certificate before you made the certificate change?

Have you tried restoring your backup (because you did make a backup ) and then reapplying the changes one at a time.

Just a few ideas for you to look at...

[farfields]

Thanks for the comments, it looks like you understand the problem I having. Please bear in mind that I'm not at all familiar with Linux or Apache. The NAS and webserver were working fine (apparently) until I wanted to replace the SSL certificate. I did not stop the webserver whilst this was being done, perhaps a mistake. The webserver was connected to port 81 locally, and mapped to port 80 by my modem.

I've made very few changes to the default Thecus setup. firmware is 2.1.09.

I didn't make any edit changes directly to any of the setup files for Apache, i.e. httpd.conf or ssl.conf.

If I run netstat -l here is the output, this does not mean a lot to me:

Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 *:49152 *:* LISTEN
tcp 0 0 N2100RAID:netbios-ssn *:* LISTEN
tcp 0 0 192.168.2.1:netbios-ssn *:* LISTEN
tcp 0 0 localhost:netbios-ssn *:* LISTEN
tcp 0 0 *:hosts2-ns *:* LISTEN
tcp 0 0 *:ftp *:* LISTEN
tcp 0 0 *:ssh *:* LISTEN
tcp 0 0 *:631 *:* LISTEN
tcp 0 0 N2100RAID:microsoft-ds *:* LISTEN
tcp 0 0 192.168.2.:microsoft-ds *:* LISTEN
tcp 0 0 localhost:microsoft-ds *:* LISTEN
udp 0 0 localhost:32768 *:*
udp 0 0 N2100RAID:netbios-ns *:*
udp 0 0 192.168.2.10:netbios-ns *:*
udp 0 0 *:netbios-ns *:*
udp 0 0 N2100RAID:netbios-dgm *:*
udp 0 0 192.168.2.1:netbios-dgm *:*
udp 0 0 *:netbios-dgm *:*
udp 0 0 *:1900 *:*
udp 0 0 *:631 *:*
udp 0 0 *:11000 *:*
Active UNIX domain sockets (only servers)
Proto RefCnt Flags Type State I-Node Path
unix 2 [ ACC ] STREAM LISTENING 3690 /var/run/ftpd.sock

Looking in /app/etc/httpd/conf/httpd.conf has the line:
#Listen 0.0.0.0:

this is puzzling. # means line is commented out, and no port number listed. Why? Have I found the 'right' file?

The ssl.conf file has line:
Listen 0.0.0.0:443

so this looks good.

If I run apachectl -k stop the response is:
httpd (no pid file) not running

If I run apachectl -k start the response is:
no listening sockets available, shutting down
Unable to open logs

the Thecus is responding to http request. i.e. an index.html file can be read from the web, and links etc work.
BUT, the Thecus web interface is not working. I guess this is where the SSL fault comes in.

Unfortunately, I don't have a backup. I'm hoping that the problem is very simple and can be fixed once I know what edit to make.

Any more help and comments welcome.

FF.

[farfields]

Progress:
I edited the httpd.conf file to enable the line:
listen 0.0.0.0:80

I can now see the Thecus webgui again.

Proves my long held belief that talking through a problem and getting some gentle hints can be just as good as having an expert fix a problem on one's behalf.

Any other advise welcome, but looks like I'm up and running again.

FF.