Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

can anyone give me an advice with this please:

I run update on my debian server by Webmin. After updating some apache2 and etc. It shows update fail.

After that I cant start apache2. I must run

netstat -ltnp | grep ':80'

Then kill pid

kill -9 1047

and now i can start apache2

When I started it first time after update some websites on fastCGI wont work I must change them in ISPconfig3 to mod-PHP and now works

NOW - I cant restart apache without kill pid.

In log of ISP I see

Unable to open logs
(98)Address already in use: make_sock: could not bind to address [::]:80   
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
 no listening sockets available, shutting down

In log of some website I see

[emerg] (13)Permission denied: mod_fcgid: can´t lock process table in pid 19264

Do you thing it will be solution update everithing by:

apt-get update

and

apt-get upgrade

to complete all updates? I have little scare if I do that then next errors will occur.


If I look at apache log i see error:

Debian Python version mismatch, expected '2.6.5+', found '2.6.6'

But that was there before that problem before.

Thanks A LOT for help.

share|improve this question
    
Using apt-get update && apt-get upgrade should be safe, because it will show you what it will do and asks if you want to continue. If this doesn't help, I would try a apt-get install --reinstall apache2. Note that none of these commands are without risk, so backup first. –  SebiF May 31 '12 at 10:07
    
[RESOLVED] I just do that apt-get update && apt-get upgrade and than was OK. –  Ripeed Jul 11 '13 at 12:42
add comment

1 Answer 1

To clarify some points,

  • Don't use kill -9 to stop a process unless you really have no other choice like it is not responding at all. It may cause data loss/corruption. Instead, you can use the script /etc/init.d/apache2 for your case
  • Doing apt-get update and apt-upgrade will provide you with the available patches and updates from debian which are mostly bug fixes and security patches.

The unable to open logs error may indicate a permission problem. Check your log files permissions and make you are starting apache with sudo.

The could not bind to address error indicates that the port is already reserved for other process. You can verify using netstat -lnp.

share|improve this answer
    
kill -9 I must use because /etc/init.d/apache2 stop dont stop it –  Ripeed May 31 '12 at 8:18
    
Doing apt-get update and apt-upgrade - I dont shure if I can run it before I fix this mess:( –  Ripeed May 31 '12 at 8:19
    
I starting apache as root –  Ripeed May 31 '12 at 8:19
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.