I have cloned linux installation from USB drive to another. The system is Fedora core and it is used as a software for encoding live stream (it's using PCI encoding cards). The system works well on original hardware configuration, however when I use this cloned flash drive on another hardware configuration one service will not start. It is a "calld" service and it is a service which has a protection which limits its execution to original hardware platform only (mac authentication probably). I need to get this service up, so when I type command "service calld starts/tatus" or "etc/init.d/calld start" I get response "service is dead and subsystems are locked". I tried matching mac address to original hardware configuration but still the same. This is a config file of service /etc/init.d/calld
I have installed httpd on Fedora 13 with yum, but it is not working when I type in a browser : localhost
Code: [comp42 html]$ sudo /etc/init.d/httpd start Starting httpd: [ OK ] [comp42 html]$ sudo /etc/init.d/httpd restart Stopping httpd: [FAILED] Starting httpd: [ OK ] [comp42 html]$ sudo /etc/init.d/httpd stop Stopping httpd: [FAILED] [comp42 html]$ sudo /etc/init.d/httpd status httpd is stopped [comp42 html]$ sudo /etc/init.d/httpd start Starting httpd: [ OK ] [comp42 html]$ sudo /etc/init.d/httpd status httpd dead but subsys locked [comp42 html]$ sudo /etc/init.d/httpd help [comp42 html]$ sudo /etc/init.d/httpd fullstatus Connection refused [comp42 html]$
Tried to reinstall several times, but nothing works. My firewall is disabled, does not work either while enabled. My httpd conf is the default one. What is going wrong?
I have installed fedora 13 recently and installed IDPS(snort) on it. But now I am not able to start service httpd. When I write service httpd start, it says OK, but I know it is a false message bcoz when I write service httpd stop it gives me Failed.
On writing service httpd status it gives a message: httpd dead but subsys locked I have tried "rm -f /var/lock/subsys/httpd" - no solution yum update hasn't solved my problem as well.
I have to show my project running at my college. And I can not understand properly the technical instructions as I am new to linux.
I also looked into the mail logs and found the following. Mar 14 10:15:43 quant dovecot: Auth process died too early - shutting down file or directory Mar 14 10:15:43 quant dovecot: child 4442 (auth) returned error 127
but I think I have a reasonable handle on the /etc/init.d, /sbin/service, chkconfig, and runlevels stuff under CentOS. However, when I install particular daemons (not part of CentOS distro), I get a weird issue. If I log in as root and do /sbin/service <daemon> status, it says "... is running...", however, if I log in as a non su, and do the same /sbin/service ... status, it says "xxx dead but subsys locked." Is the daemon running or not? I assume it's some kind of privilege issue with how the daemon is setup versus the non root login.I would like to have users be able to use service to query daemon status as works with the base daemons like sshd and httpd.
I have centos 5.5 64bit installed. When I start the httpd service I get the above message. The message is bogus because the server is running and web pages work. Is there a fix out there to resolve this?
I've got a box with a fresh installation of CentOS 5.6, but had several configs copied from an old 4.8 box that I've now got to finish. Most everything seems fine, but I can't get apache running. It reports that it starts up fine, but immediately stops and reports "httpd dead but subsys locked"Most of the advice I've found while searching suggests to just delete the http.pid file and restart, which doesn't help in my case. I did find a few problems where SELinux was restricting httpd from creating or touching certain files (I found reports in /var/log/messages) but I've worked through that.
So the big question here is: /var/log/messages and /var/log/httpd/error_log are now empty, and don't show any more errors when I restart httpd. Does anyone know where else I can look for reporting/logging on what's happening to httpd to cause it to die?
When I look the Services panel, nxserver is listed but shows as "Service is Dead". Does this mean anything specifically? Could it be related to firewall or security issues? Right above it a related program to nxserver, nxsensor, is listed and it's shown as operational.
Same thing here in my Services panel. Just getting into using NX...the display seems near Win RDP quality over the home lan. I'm now trying to get the sound to work. What is this 'dummy output' in my Sound preferences and where did my sound cards go? I have one onboard sc and a PCI card, neither recognized via the NX client session. Looking to get ESD going which might be the issue.
I have opened up the Service Configuration window that shows all the services and their status. My httpd says that it is enabled, but also that "this service is dead" and there is a orangish triangle. I can run phpMyAdmin on my server, but I can't run it from any other PC on my network.
i just installed Fedora 12, clean without anything change in it. I opened services dialog, and the openvpn service have status:dead, however it shows that it is enabled.when i try to run it as:/sbin/service openvpn start.It write OK. However if check it:/sbin/service openvpn status it write that service not running. What is a point of a problem? I have opened openvpn in FireWall,however without success, may be some additionsl services for openvpn are not running?
My mail server is getting problem since 3 days. It automatically get hang and httpd service get dead any time. How I can check what is effecting server, load, network traffic etc...
I am using CentOS 5.6 with Apache 2.2.17. The Apache was compiled from source using RPM build to comply with PCI requirements. Also Plesk 9.3 is used as a control panel, but other than the config files the Apache is pretty standard. When the httpd is started, there are no errors reported in /var/log/messages or in the error_log, and the httpd starts, shows up in ps and the pid file exists in /var/run/httpd.pid.
However when you check the status 'service httpd status' you get 'httpd dead but subsys locked'. You can add websites normally, and the proper config files are generated so I am pretty sure this isn't a control panel issue as I have other servers running the same control panel and Apache 2.2.16 compiled and installed the same way as the 2.2.17 and there are no problems.
i have squid running in my network the problem i am facing is that once a week the squid service is dead, i checked the log files bu could not figure out what the problem is it gives me the error squid dead but pid file exist squid error no running copy i have written a script that just moves the compressed log files from the /var/log/squid files to /media/usbdisk the script is as follows i suspect that this problem arises because of the script coz the script runs every week and the next day i get this problem
My part time hobby PC, running FC12, has started misbehaving following some recent updates. I hadn't booted the machine for about 10 days. It booted OK, I checked for updates, applied them, and then my problems started.When I boot now I get LONG delays after logging in and eventually will get the following error:
Could not display "x-nautilus-desktop:///". Error DBus error.org.freedesktop.DBus.Error.NoReply:
Did not receive a reply, etc, etc...Have tried re-installing Nautilus, same problem. Being a relative Linux (though not Unix) newbie, what is Nautilus? Do I need it? Can I just get rid of it? Is there an alternative I can install that does work?
I know that this topic has been posted, responded to, and maybe even resolved, many times here, but I am stuck here with partially dead fileserver and need some pointers.
Problem: one disk drive that was part of a logical volume died. I have a replacement, but I can't get it into the LV and get the LV back up again.
pvcreate --uuid <uuid of dead drive> /dev/sdX1, where /dev/sdX1 is the newly created drive and its partition. vgcfgrestore VolGroup vgscan VolGroup vgchange -ay VolGroup e2fsck /dev/mapper/VolGroup-LogVol
but, e2fsck can't find a superblock. Apparently this drive is the first in the LV sequence, and it is not formatted as part of the LV.
So how to I get this new disk formatted into the LV without reformatting the entire LV and losing what data I still have?
I've got a problem with samba and the nmb service. My system boots in Gnome
Ive set up Samba and it works ok, untill I reboot, then I have to go into services and restart Nmb service. the services bit says its dead after a reboot, its running on run levels 2345 I had a few hicups setting it up took me a couple of days to figure out the fire wall and SElinus were blocking things, so I ticked all the samba things - and it works a whole lot better.
I have to admit its a whole lot more polished than last time I tried linux - Red Hat 5. I like the Yum installer it takes a lot of guess work out for us novices, one thing I would like is to be able to edit and open things as root in Gnome or just log into it as root so that you can set things up, but I'll save that question for another day.
I have Fedora 11. After my most recent update, I can't log in. Every time I authenticate, the logon window disappears, the screen goes black briefly, and then I am back at the log in window I entirely reinstalled, and then it worked, until I updated to the newest kernel then it didn't work anymore. Update: I now generated a xorg.conf with system-config-display --noui I manually removed and reinstalled xorg-x11-drv-intel with yum. It didn't work. By the way: now the start hangs on "Starting atd: OK" If I specify "vesa" in xorg.conf, then it gets past the point, but display doesn't load properly.
I have FC 12 install on a Compaq nx9600 that comes with a Broadcom BMC4306 wireless card. I'm not sure what my kernel is, but I have all of the updates for FC 12.Whenever my laptop resumes from Hibernation/Suspend my Enable Wireless check box in the Network Manager is greyed out and it will not come back till I reboot the computer. Is there any one out there that can help with this problem, as I do not want to disable my Hibernation/Suspend as I tend to forget to turn the laptop off for a few days on end, and this beast sucks a lot of power so it is a drain on my power bill.
I have been running Fedora 12 on my HP Proliant DL140 Server for about 6 months now without any issues, yesterday I ran yum update and rebooted afterwards but the server now wont boot
I'm having major network issues. I cannot get a real IP address with this RHEL installation I have. Im using a Braodcom NetLink ethernet card and the tg3 driver that came with my install cd. When I go to services it says my NetworkManager is enables but dead.
Since I started using Fedora 10 I can't login as root. Even though the system recognizes the root password when it requires it for certain administrative tasks it refuses to let me login as root.
When I try to edit httpd.conf I get the message "could not save file..." it doesn't even prompt me for the root password. My httpd service is dead and I can't resurrect it, what should I do?
I find myself in the strange position of having an old P4 system that I want to throw Fedora 10 on - it's a considerable upgrade from the old 866Mhz P3 that I've been using to do some number crunching on. (It's a personal project, but it's CPU intensive, so the P4 is a welcome upgrade.) My problem with it is that the motherboard's AGP socket is dead, and I can't find a PCI graphics card, so I'm trying to do a totally headless install - I have no idea what errors may be shown, if any. All I know is that whatever I've tried up till now hasn't worked.
1. Remove the hard drive from the P4, stick it into a spare, semi working system (AMD Athlon, RAM isn't working too well), install F10 on the hard drive, remove the drive, put it back into the P4, and let it boot. Results: Nothing. No DHCP announcement, so I don't know if it's done anything.
2. Try a variation of a PXE boot using the vnc parameter. I've copied the instructions here with no luck. Tried it using a nearby mirror (mirror.nus.edu.sg) as well as method=cdrom, with no luck on either. Results: Also nothing.Should I give up on this, or is there anything else I should try?
After booting I noticed that sometimes nmb was not running. The command # service nmb status gives nmbd dead but pid file exists The timestamp of the pid file suggests that at the last shutdown the pid file was not removed, and I guess this prevented nmb to start properly during booting (Although during booting the messages is [OK]).
If I shut down nmb manually, everything is fine. I checked the log in /var/log/samba/log.nmbd and it doesn't show any error. As mentioned, this occurs only occasionally, and I have no idea what may be causing this.
