Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a fresh install of CentOS 4.6 (final) with cPanel/WHM installed. Once
the server boots up, everything seems to be going good, Although cpsrvd fails,
throughout the hour since the boot, the server seems to stop. cPanel/WHM is not
accessible nor is ssh, basically i think the services all stop. Within 1-2
hours of this happening it goes back to normal and repeats again.
I do not have a firewall installed. I disabled all firewalls known.
(i have reformatted up to 3-4 times to try and fix this issue, but same
proccess repeats)
- boot up server
- cpsrvd fails
- cPanel works normally
- within a time period (1 hour or less) cPanel/WHM is not accessable nor can i
access SSH.
- within 1-2 hours everything goes back to normal.
- same proccess repeats.
(yesturday it lasted 22 hours successfully) but the same proccess repeated
today.
Last edited by RobertNikic; 06-23-2008 at 04:38 PM.
firstly, please don't use words like "urgent", it's generally considered rude in a voluntary community.
secondly, what sort of architecture are you running? is this a dedicated colo server, a vm i guess? it sounds a lot more like a network issue than anythign on the server itself. a duplicate IP which you get lucky from sometimes when the arp entry times out on the local router. that fits in just about exactly with the symptoms you describe, and I can't think of any other good reason. You might want to do something like set up a continual ping. every few seconds, ping google.com and write the output to a file. If you then get disconnected from the server, once you get back in you would be able to look at the file and see if it could ping anything. also does the server reboot? anythign added to dmesg or /var/log/messages?
I am running a AMD Athlon 64 X2 3800+ Dual Core Processor at my location meaning i have full access to it and i can restart it.
I am running 3 diffrent ip addresses on it.
SERVER1 IP ADDRESS
DNS1 IP ADDRESS
DNS2 IP ADDRESS
and it cannot also find \var\log\messsages on the server.
(note: im not very good with linux)
EDIT: i restarted the server and it worked for about 5 minutes or so?
do you know what command i can do so i can check my log messages so i can see what the issue is?
Last edited by RobertNikic; 06-23-2008 at 05:09 PM.
[root@server1 ~]# tail /var/log/messages
Jun 23 18:14:51 server1 portsentry[3609]: adminalert: ERROR: No UDP ports supplied in config file. Aborting
Jun 23 18:14:51 server1 portsentry[3609]: adminalert: ERROR: could not go into PortSentry mode. Shutting down.
Jun 23 18:14:51 server1 portsentry[3609]: securityalert: Psionic PortSentry is shutting down
Jun 23 18:14:51 server1 portsentry[3609]: adminalert: Psionic PortSentry is shutting down
Jun 23 18:14:51 server1 portsentry: Starting portsentry -udp: succeeded
Jun 23 18:14:52 server1 fstab-sync[3614]: removed all generated mount points
Jun 23 18:14:52 server1 fstab-sync[4226]: added mount point /media/cdrecorder for /dev/hda
Jun 23 18:14:59 server1 login(pam_unix)[3621]: session opened for user root by LOGIN(uid=0)
Jun 23 18:14:59 server1 -- root[3621]: ROOT LOGIN ON tty1
Jun 23 18:15:32 server1 sshd(pam_unix)[4415]: session opened for user root by (uid=0)
[root@server1 ~]# tail -20 /var/log/messages
Jun 23 18:14:50 server1 startmailman: Starting Mailman's master qrunner.
Jun 23 18:14:50 server1 cpanel: Starting mailman services: succeeded
Jun 23 18:14:50 server1 messagebus: messagebus startup succeeded
Jun 23 18:14:51 server1 haldaemon: haldaemon startup succeeded
Jun 23 18:14:51 server1 portsentry[3604]: adminalert: Psionic PortSentry 1.1 is starting.
Jun 23 18:14:51 server1 portsentry[3605]: adminalert: Going into listen mode on TCP port: 1
Jun 23 18:14:51 server1 portsentry[3605]: adminalert: Going into listen mode on TCP port: 111
Jun 23 18:14:51 server1 portsentry[3605]: adminalert: PortSentry is now active and listening.
Jun 23 18:14:51 server1 portsentry: Starting portsentry -tcp: succeeded
Jun 23 18:14:51 server1 portsentry[3608]: adminalert: Psionic PortSentry 1.1 is starting.
Jun 23 18:14:51 server1 portsentry[3609]: adminalert: ERROR: No UDP ports supplied in config file. Aborting
Jun 23 18:14:51 server1 portsentry[3609]: adminalert: ERROR: could not go into PortSentry mode. Shutting down.
Jun 23 18:14:51 server1 portsentry[3609]: securityalert: Psionic PortSentry is shutting down
Jun 23 18:14:51 server1 portsentry[3609]: adminalert: Psionic PortSentry is shutting down
Jun 23 18:14:51 server1 portsentry: Starting portsentry -udp: succeeded
Jun 23 18:14:52 server1 fstab-sync[3614]: removed all generated mount points
Jun 23 18:14:52 server1 fstab-sync[4226]: added mount point /media/cdrecorder for /dev/hda
Jun 23 18:14:59 server1 login(pam_unix)[3621]: session opened for user root by LOGIN(uid=0)
Jun 23 18:14:59 server1 -- root[3621]: ROOT LOGIN ON tty1
Jun 23 18:15:32 server1 sshd(pam_unix)[4415]: session opened for user root by (uid=0)
Tail shows the end of the log file (hence the name), but there isn't a lot of point posting the results unless something's just happened, like a service has died
Similalry for the grep version, if you have a problem with a service, grep for that service
[root@server1 ~]# tail /var/log/messages
Jun 23 18:14:51 server1 portsentry[3609]: adminalert: ERROR: No UDP ports supplied in config file. Aborting
Jun 23 18:14:51 server1 portsentry[3609]: adminalert: ERROR: could not go into PortSentry mode. Shutting down.
Jun 23 18:14:51 server1 portsentry[3609]: securityalert: Psionic PortSentry is shutting down
Jun 23 18:14:51 server1 portsentry[3609]: adminalert: Psionic PortSentry is shutting down
Jun 23 18:14:51 server1 portsentry: Starting portsentry -udp: succeeded
Jun 23 18:14:52 server1 fstab-sync[3614]: removed all generated mount points
Jun 23 18:14:52 server1 fstab-sync[4226]: added mount point /media/cdrecorder for /dev/hda
Jun 23 18:14:59 server1 login(pam_unix)[3621]: session opened for user root by LOGIN(uid=0)
Jun 23 18:14:59 server1 -- root[3621]: ROOT LOGIN ON tty1
Jun 23 18:15:32 server1 sshd(pam_unix)[4415]: session opened for user root by (uid=0)
________________________
the above in red, could that be whats casuing everything to go offline and un accessible?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.