I'm completely stumped by a problem with httpd in Fedora 13. It fails to start on boot: I can see: Starting htpd: FAILED, in /var/log/boot.log, but I can't find anything else in messages, audit.log or anywhere else that gives me any clue why. The weird thing is that running:
run_init service httpd start
after boot _works_ and the server runs fine, but even when it's running OK,
service httpd status
reports
httpd dead but subsys locked
I'm guessing that the problem somehow relates to selinux, but I can't find anything in the audit logs that gives me a clue. How to turn on more logging so that I can get closer to the problem. I finally discovered the cause. This system was originally configured to use network services directly, without NetworkManager. It had been upgraded a number of times since installation. It seems that over time, if you have turned off NetworkManager, the defaults have changed. Used to be that the network services was 'enabled' by default (hence started at run time). Now, the default is 'disabled'. Httpd couldn't start because there was no network to start on. Enabling network services at boot time fixed this. I guess I should have noticed this. But one might think that httpd failing to start because of the lack of a network might at least give a warning message in the logs about the reason.
I have just installed Fedora 11 on a "fresh machine" and everything works ok, except for Apache httpd the message seen in the error_log is the following: Name or service not known: mod_unique_id: unable to find IPv4 address of "myserver"
I have one problem regarding my web server. When I am try to restart my httpd service it shows...
[root@localhost ~]# service httpd restart Stopping httpd: [FAILED] Starting httpd: (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80 no listening sockets available, shutting down Unable to open logs [FAILED] [root@localhost ~]#
I have installed fedora 13 in my system. httpd server is also installed. when I tried to start the service of httpd, following error message displayed: Starting httpd: (98)Address already in use: make_sock: could not bind to address [::]:80
I am running fedora 10 and webmin squid proxy server, after power failure the squid fails to start. i have tried to start it from command line but failed
Ejabberd fails to start in f-12. ejabberd-2.0.5-9.fc12.i686. This ran fine in f-10 and f-11. Getting a large number of strange error messages from the ejabberd log code...
Looks like it may be a permissions problem.
Anybody from the ejabberd community here that has gotten ejabberd to work on f-12?
I turned my home PC running Ubuntu 10.04 into a server, and so i am so lost, after reading like a 10-20 different guides and/or official docs, I am totally lost.
All I wanted was to create a custom 404 error page...i read about how people edited .htaccess files to customize error pages, i tried and failed also, editing apache2.conf, I got lost and i dont wanna mess up everything and also, how you're supposed to not touch either of those as its not how it should be done and instead you need to edit httpd.conf and i did and FAILED! again...
Also how do I make it so that I can make subdomain(s) on my site? and wth is a name server and where do I get one?
Alright, so I installed the c5-testing versions of httpd, php, and mysql, since my server is used for other daemons primarily and these aren't used as production servers I decided to test the bleeding edge versions of these, report any bugs I find, etc. The problem is, since I updated httpd and mysqld they no longer start up at boot. I tried using chkconfig --add with both of them, but both their init.d scripts have - for levels, so I did not assign any levels. They still do not start up at boot. [URL]
Arpwatch is failing to start at boot time. I got this message:
arpwatch: bad interface eth0: eth0: no ipv4 address assigned
Once I login into my account, I can (as root) run the arpwatch demon, but it is suppose to run at boot time. After I installed aprwatch, it was working correctly. I do not have an idea of what happens or since when the problem start to happen. I just realize, after a while , that arpwatch was not running. I am running Fedora 12 - 2.6.32.9-67.fc12
I am trying to get SQL-Ledger installed and running on my computer, which needs PostgreSQL installed to run.Currently, I am having trouble with it starting at boot-up. How can I access the appropriate log files in order to figure out what's wrong?
Also, I need to know what httpd is, and who the owner and groups using that might be on my system.
I have the Samba server & users configured, I can access between Linux/Windows shares and both SMB & NMB services are set to be enabled at boot.Everything working.But when I restart the computer, I notice in services configuration that "This service is dead." for NMB. Therefore I have to enable it manually upon boot so that it works.I'm using Fedora 10, fresh installed and updated. I've noticed through search that others have had this issue as well throughout other versions of Fedora, yet I have not found a conclusive solution to this.
I rebuilt my box with Fedora 14. installed httpd, mysql php etc. when I tried to start my httpd it was giving me error about finding the root document and server name I was able to fix temp the issue with the name by placing ServerName 192.168.1.105:80 in the httpd.conf file and the root document somehow was fixed also. but I am still can't start the httpd and no error message except that it failed. I also disabled Selinix but still no luck.
How to resolve this apache2 problem I keep getting, I have installed a debian LAMP server with ispconfig3 and everytime I reboot apache fails to start, I don't know and I have done some research but nothing seems to work, which leads me to reinstall everything from scratch again, I think I have reinstalled at least 10x or more.
I have Fedora 12 x86_64 installed in my computer. I have also installed system-config-httpd, but when I go to System --> Administration --> Server Settings --> HTTP, nothing shows up.
Can anyone help me with how to create an init.d script that will startup a vm machine in virtualbox at boot? I found this script:[URL]..But it is for ubuntu. I am running fedora 12 x386 and using it as an Amahi server. Very cool, but it would be extra cool if I had a virtual windows machine startup when I booted up this server. Then I could just rdp into it when I needed something in windows.
I've just upgraded to 9.10, and mysql fails to start. When I do an /etc/init.d/mysql start, I just get * Starting MySQL database server mysqld ...fail!with no additional errors or information to say what went wrong. I saw this thread http://ubuntuforums.org/showthread.php?t=1322070 but the fix mentioned does not apply, as I don't have the #skip bsd line in my config file.
My ubuntu server was working normally but it suddenly failed to start, stopping after the following message: init: ureadahead-other main process (587) terminated with status 4 after this message, the system halts and does not finish the start up processes.
If I start the server in recovery mode, I get: init: ureadahead-other main process (587) terminated with status 4 [ 21.892940] ACPI: I/O resource w83627hf [0x295-0x296] conflicts with ACPI region HWMI [0x295-0x296] the system also halts and does not start. Right now, I can not use the server at all.
httpd have been install by default and I don't start it as services. I have install apache2 but don't want to start as service, I can't add it into the chkconfig. When I try to remove httpd, fedora also want to remove these software.
gnome-user-share i586 2.26.0-2.fc11 installed 809 k httpd-manual i586 2.2.11-8 installed 3.5 M mod_perl i586 2.0.4-8 installed 6.3 M
[code]....
php and webalizer I don't care as I want to install the new version, but is their any problem removing the other one? Also I want to pount the apache2 documentroot to var/www/httpd but when I do this and try to see the website I got a 403 error (not autorize)
I just did a clean install of FC12 x86_64 and want to configure tomcat to run behind apache httpd. What is the easiest way to accomplish this? I'm a newbie at server configuration so detailed instructions would be nice
I've just setup Fedora 10 x64 on a Supermicro 7045 with dual nic; I setup a web site and ran into a strange problem; I can't see my website from outside my LAN; checking IP on Internet it sees my IP as coming for my dynamic IP (IP of router/switch) and not my static IP.
eth0: Static IP eth1: Dynamic IP
These are standard Intel 82563EB Dual-Port Gigabit Ethernet Controller.
Is there a way to specify the order in which it sees the nic ports?
I'm wonder if I can mix Static and Dynamic IP's; on the outside they resolve to a static IP; the dynamic one shows up as my router/switch IP; but it allows me to access my DHCP computers; this isn't a web server; but a development machine for writing PHP apps.
Where 123.123.123.3 is my static IP address.
I should mention that nmap -v -p 80 123.123.123.3 shows an open port on 80
Has anyone noticed that when using NameVirtualHost's in apache that the service httpd restart command is broken?Also it seems system-config-bind has glitches too.
I just installed FC12 x86_64. After a clean install I found that httpd, mysql, svn, svnadmin, etc are already installed. I still need to install and configure tomcat running as a worker behind httpd and configure everything. But my question is about security. What do I need to do to ensure that when I start httpd and mysql that they are secure? Are there default settings that I need to change? Are there security patches I need to apply?
System Config: Fedora Core 12 x86_64 AMD Athlon II X2 250 3.0 GHz dual core GIGABYTE GA-MA785GM-US2H G.SKILL 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 1066 (PC2 8500) Dual Channel Kit Desktop Memory Model F2-8500CL5D-4GBPK
I have Apache Server working online under Fedora Core 6. But before I installed and configured everything, I've been testing in Fedora 12. The problem surges here, when I start the httpd service, every supuse 404 action on a web browser, takes me to localhost. I mean, if I enter google.com, no error, just goes to localhost, http://asdasd, no error, gives back localhost. I used to ignore the problem 'cause I thought it was a problem on my apache, but when I installed the Server on the Fedora Core 6 machine, I found that I have the same problem there. Of course, it only occurs when I am browsing through the same machine that has httpd started. Does anyone know how to change that??
Alright, so I upgraded my old fedora 10 server to Fedora 11 with a netinstall CD, but now service httpd restart is broken. I already had to delete the old config file and reinstall apache, but now I can't restart it. I can kill it and then start it manually, but it never stops the running instance and fails to bind the port. I know it's because /var/run/httpd/htpd.pid is in the wrong place, which would be /var/run/httpd.pid, but do I have to make a symlink every time I want to restart it? I edited all the config files to point to the right place, but the system does not honor them. What do I do?
On F13 i386 inside Virtualbox. Host is a Win7 x64 box.
This may just be more idle curiosity than anything else since the server still works. . . but it's really bothering me because I can't explain it.
My (limited) understanding is that the devel files are just the source files and shouldn't actually affect peformance.
Yet, prior to installing httpd-devel (and its dependencies), /etc/init.d/httpd restart takes about 2 seconds total. After installing httpd-devel, the "stopping" phase of the httpd restart take 5-7 seconds (which seems really long when you're just sitting there waiting on it.
yum install httpd-devel also installs the following for dependencies: db4-cxx db4-devel cyrus-sasl-devel apr-devel apr-util-devel openldap-devel expat-devel
All but one of those are devel files as well. And here's the real kicker: Uninstalling them through YUM doesn't put things back to normal (even after reboot).
I'm no linux expert. But I wouldn't think installing devel files would have this effect or any effect like this since they're just source code files (?). Can anyone explain what's happening or give me tips on how I can watch the apache process stop and see what's hanging it up?
