Re: [CentOS] How to determine why a server is not responding
On 12 Apr 2013, at 10:03, John R Pierce wrote: > On 4/12/2013 1:38 AM, Nicolas Mitchell wrote: >> non-standard location when Plesk is installed > > I don't think thats the only nonstandard thing when Plesk is in use, No, it isn't, yet there's things available that'll help you find what you need. > in > fact, I think it makes so many changes to CentOS thats its very hard to > provide CentOS support for the Plesk system. > Or on any system that has been touched by human hands? I know what you mean, but you gotta lend a hand. Nic > > -- > john r pierce 37N 122W > somewhere on the middle of the left coast > > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to determine why a server is not responding
On 4/12/2013 1:38 AM, Nicolas Mitchell wrote: > non-standard location when Plesk is installed I don't think thats the only nonstandard thing when Plesk is in use, in fact, I think it makes so many changes to CentOS thats its very hard to provide CentOS support for the Plesk system. -- john r pierce 37N 122W somewhere on the middle of the left coast ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to determine why a server is not responding
Hello there, Is there anything in the Apache logs indicating a problem? I think the logs might be in a non-standard location when Plesk is installed so you'll need to check for where those are. I think I remember having a problem, on a similar configuration, with a PHP limit and a user trying to send a large attachment through Horde that resulted in an almighty slowdown. Anyway, my twopenny'orth. All the best, Nic On 12 Apr 2013, at 07:32, nan del bosc wrote: > Alexander Dalloz, true, but I'm only a system administrator guy who do the > work that tells the boss... ;) > > Kai Schaetzl, yes! you are right, I should have said this in the beginning! > Sorry, it's because of the hurry... ;) > > Thank's for all your answer! I wrote a mail to my provider. I keep you > informed! > > > 2013/4/11 Dale Dellutri > >> On Thu, Apr 11, 2013 at 10:59 AM, nan del bosc >> wrote: >> >>> ... >>> This is a Virtual Server from 1and1, I cannot access the BIOS... >>> >>> any other idea? >> >> If this is a virtual server, the actual hardware may just be running >> other virtual servers and you're not getting any resources. If that's >> true, nothing you do from your server will help you. You'll need to >> get system stats from the actual hardware provider. >> >> Sounds like the hardware is over-committed. Do you have some >> kind of service guarantee? >> >> -- >> Dale Dellutri >> ___ >> CentOS mailing list >> CentOS@centos.org >> http://lists.centos.org/mailman/listinfo/centos > > > > -- > --- > Salut! > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to determine why a server is not responding
Alexander Dalloz, true, but I'm only a system administrator guy who do the work that tells the boss... ;) Kai Schaetzl, yes! you are right, I should have said this in the beginning! Sorry, it's because of the hurry... ;) Thank's for all your answer! I wrote a mail to my provider. I keep you informed! 2013/4/11 Dale Dellutri > On Thu, Apr 11, 2013 at 10:59 AM, nan del bosc > wrote: > > > ... > > This is a Virtual Server from 1and1, I cannot access the BIOS... > > > > any other idea? > > > > If this is a virtual server, the actual hardware may just be running > other virtual servers and you're not getting any resources. If that's > true, nothing you do from your server will help you. You'll need to > get system stats from the actual hardware provider. > > Sounds like the hardware is over-committed. Do you have some > kind of service guarantee? > > -- > Dale Dellutri > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > -- --- Salut! ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to determine why a server is not responding
On Thu, Apr 11, 2013 at 10:59 AM, nan del bosc wrote: > ... > This is a Virtual Server from 1and1, I cannot access the BIOS... > > any other idea? > If this is a virtual server, the actual hardware may just be running other virtual servers and you're not getting any resources. If that's true, nothing you do from your server will help you. You'll need to get system stats from the actual hardware provider. Sounds like the hardware is over-committed. Do you have some kind of service guarantee? -- Dale Dellutri ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to determine why a server is not responding
Nan del bosc wrote on Thu, 11 Apr 2013 17:59:58 +0200: > This is a Virtual Server from 1and1, You should have said this in the beginning! Can you be sure that this is a standard CentOS and not a version catered by the provider? It may just be a problem with the virtualizing software. You should talk to them. They also have means to access it in this hanging state from the host machine that you don't have. Kai ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to determine why a server is not responding
nan del bosc wrote: > Thank's for your quick answer! > > I can't use ipmi in this machine... > > # modprobe ipmi_si > FATAL: Error inserting ipmi_si > (/lib/modules/2.6.18-194.26.1.el5xen/kernel/drivers/char/ipmi/ipmi_si.ko): > No such device Um, no: yum install OpenIPMI service ipmi start ll /dev/ipmi0. > This is a Virtual Server from 1and1, I cannot access the BIOS... Wait - this is hosted, not something you can lay your hands on? In that case, you need to call the hosting provider and complain. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to determine why a server is not responding
Am 11.04.2013 17:36, schrieb nan del bosc: > Hi to all! > > We're using CentOS 5.5 64bits for our Plesk 11. That's insane! Why on earth do you run a 2,5 years old unpatched public system? You are asking for trouble and innocent third will be the victims of your hacked system. > This week we had the following problem 3 times... > > Suddenly, the server stops responding in all services (SSH, Apache, > Postfix, ...) but ping works! > > After wait a few minutes (or 2 hours some times) the server continues > unresponsive until we reboot. After reboot we search on /var/log/messages > but cannot find useful information... > > Apr 11 14:56:05 s1 postfix/smtpd[8263]: SQL engine 'intentionally disabled' > not supported > Apr 11 14:56:05 s1 postfix/smtpd[8263]: auxpropfunc error no mechanism > available > Apr 11 14:56:42 s1 postfix/smtpd[8370]: SQL engine 'intentionally disabled' > not supported > Apr 11 14:56:42 s1 postfix/smtpd[8370]: auxpropfunc error no mechanism > available > Apr 11 14:56:47 s1 postfix/smtpd[8391]: SQL engine 'intentionally disabled' > not supported > Apr 11 14:56:47 s1 postfix/smtpd[8391]: auxpropfunc error no mechanism > available > Apr 11 14:56:47 s1 postfix/smtpd[8392]: SQL engine 'intentionally disabled' > not supported > Apr 11 14:56:47 s1 postfix/smtpd[8392]: auxpropfunc error no mechanism > available > Apr 11 16:55:42 s1 syslogd 1.4.1: restart. > Apr 11 16:55:42 s1 kernel: klogd 1.4.1, log source = /proc/kmsg started. > Apr 11 16:55:42 s1 kernel: Bootdata ok (command line is ro root=/dev/xvda1 > console=xvc0 console=hvc0 xencons=hvc) > Apr 11 16:55:42 s1 kernel: Linux version 2.6.18-194.26.1.el5xen ( > mockbu...@builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat > 4.1.2-48)) #1 SMP Tue Nov 9 13:35:30 EST 2010 That's a Xen Domain. So IPMI, as suggested by others, will not work. > Apr 11 16:55:42 s1 kernel: BIOS-provided physical RAM map: > Apr 11 16:55:42 s1 kernel: Xen: - 8000 > (usable) > Apr 11 16:55:42 s1 kernel: No mptable found. > Apr 11 16:55:42 s1 kernel: Built 1 zonelists. Total pages: 524288 > Apr 11 16:55:42 s1 kernel: Kernel command line: ro root=/dev/xvda1 > console=xvc0 console=hvc0 xencons=hvc [ ... ] > What can we do? what can we test? First, update your system to the latest 5.9 + updates! Talk to your hoster. If your Xen VM has issues other guests on the same hardware may have too. Or another VM on the hosts consumes so much resources that your VM does not respond any longer. [ ... ] > Thank's! > > -- > --- > Salut! Alexander ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to determine why a server is not responding
> We're using CentOS 5.5 64bits for our Plesk 11. > > This week we had the following problem 3 times... > > Suddenly, the server stops responding in all services (SSH, Apache, > Postfix, ...) but ping works! > > After wait a few minutes (or 2 hours some times) the server continues > unresponsive until we reboot. After reboot we search on > /var/log/messages > but cannot find useful information... ... > > What can we do? what can we test? Could be something related to disk access or RAM, runaway process or whatever. Do you have any system monitoring tools installed? Like munin, atop, sysstat? Any kernel errors in the logs? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to determine why a server is not responding
On Thu, Apr 11, 2013 at 10:36 AM, nan del bosc wrote: > Hi to all! > > We're using CentOS 5.5 64bits for our Plesk 11. > > This week we had the following problem 3 times... > > Suddenly, the server stops responding in all services (SSH, Apache, > Postfix, ...) but ping works! > > After wait a few minutes (or 2 hours some times) the server continues > unresponsive until we reboot. After reboot we search on /var/log/messages > but cannot find useful information... > ... > What can we do? what can we test? Are you running sysstat / sar ? Perhaps the sa / sar database that's left after reboot can show if some resource was over capacity. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to determine why a server is not responding
Thank's for your quick answer! I can't use ipmi in this machine... # ipmitool sel Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory Get SEL Info command failed # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/2.6.18-194.26.1.el5xen/kernel/drivers/char/ipmi/ipmi_si.ko): No such device # lsmod |grep ipmi ipmi_watchdog 52641 0 ipmi_devintf 44753 0 ipmi_msghandler73369 2 ipmi_watchdog,ipmi_devintf This is a Virtual Server from 1and1, I cannot access the BIOS... any other idea? 2013/4/11 > nan del bosc wrote: > > Hi to all! > > > > We're using CentOS 5.5 64bits for our Plesk 11. > > > > This week we had the following problem 3 times... > > > > Suddenly, the server stops responding in all services (SSH, Apache, > > Postfix, ...) but ping works! > > > > After wait a few minutes (or 2 hours some times) the server continues > > unresponsive until we reboot. After reboot we search on /var/log/messages > > but cannot find useful information... > > > A quick google shows me that the postfix messages are just that, and you > might want to fix it so it's not asking for it. > > HOWEVER, the important thing is that it appears to have just gone > completely unresponsive. I've seen that happen to some servers here, and > we've never found any clues On the other hand, IIRC, they tended to be > boxes that we've had other problems with, and have had a number rebuilt > under warranty (mostly Penguins, and the problems I've had with them, as > they're all Supermicro m/b's, told me to NEVER buy a Supermicro m/b). > > The only thing I can suggest trying might be to use ipmitool (assuming you > don't want to bring them down and look in the BIOS) to read the SEL > (system event log), to look for hardware errors. > > mark > > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > -- --- Salut! ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to determine why a server is not responding
nan del bosc wrote: > Hi to all! > > We're using CentOS 5.5 64bits for our Plesk 11. > > This week we had the following problem 3 times... > > Suddenly, the server stops responding in all services (SSH, Apache, > Postfix, ...) but ping works! > > After wait a few minutes (or 2 hours some times) the server continues > unresponsive until we reboot. After reboot we search on /var/log/messages > but cannot find useful information... A quick google shows me that the postfix messages are just that, and you might want to fix it so it's not asking for it. HOWEVER, the important thing is that it appears to have just gone completely unresponsive. I've seen that happen to some servers here, and we've never found any clues On the other hand, IIRC, they tended to be boxes that we've had other problems with, and have had a number rebuilt under warranty (mostly Penguins, and the problems I've had with them, as they're all Supermicro m/b's, told me to NEVER buy a Supermicro m/b). The only thing I can suggest trying might be to use ipmitool (assuming you don't want to bring them down and look in the BIOS) to read the SEL (system event log), to look for hardware errors. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] How to determine why a server is not responding
Hi to all! We're using CentOS 5.5 64bits for our Plesk 11. This week we had the following problem 3 times... Suddenly, the server stops responding in all services (SSH, Apache, Postfix, ...) but ping works! After wait a few minutes (or 2 hours some times) the server continues unresponsive until we reboot. After reboot we search on /var/log/messages but cannot find useful information... Apr 11 14:56:05 s1 postfix/smtpd[8263]: SQL engine 'intentionally disabled' not supported Apr 11 14:56:05 s1 postfix/smtpd[8263]: auxpropfunc error no mechanism available Apr 11 14:56:42 s1 postfix/smtpd[8370]: SQL engine 'intentionally disabled' not supported Apr 11 14:56:42 s1 postfix/smtpd[8370]: auxpropfunc error no mechanism available Apr 11 14:56:47 s1 postfix/smtpd[8391]: SQL engine 'intentionally disabled' not supported Apr 11 14:56:47 s1 postfix/smtpd[8391]: auxpropfunc error no mechanism available Apr 11 14:56:47 s1 postfix/smtpd[8392]: SQL engine 'intentionally disabled' not supported Apr 11 14:56:47 s1 postfix/smtpd[8392]: auxpropfunc error no mechanism available Apr 11 16:55:42 s1 syslogd 1.4.1: restart. Apr 11 16:55:42 s1 kernel: klogd 1.4.1, log source = /proc/kmsg started. Apr 11 16:55:42 s1 kernel: Bootdata ok (command line is ro root=/dev/xvda1 console=xvc0 console=hvc0 xencons=hvc) Apr 11 16:55:42 s1 kernel: Linux version 2.6.18-194.26.1.el5xen ( mockbu...@builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-48)) #1 SMP Tue Nov 9 13:35:30 EST 2010 Apr 11 16:55:42 s1 kernel: BIOS-provided physical RAM map: Apr 11 16:55:42 s1 kernel: Xen: - 8000 (usable) Apr 11 16:55:42 s1 kernel: No mptable found. Apr 11 16:55:42 s1 kernel: Built 1 zonelists. Total pages: 524288 Apr 11 16:55:42 s1 kernel: Kernel command line: ro root=/dev/xvda1 console=xvc0 console=hvc0 xencons=hvc Apr 11 16:55:42 s1 kernel: Initializing CPU#0 Apr 11 16:55:42 s1 kernel: PID hash table entries: 4096 (order: 12, 32768 bytes) Apr 11 16:55:42 s1 kernel: Xen reported: 2009.260 MHz processor. Apr 11 16:55:42 s1 kernel: Console: colour dummy device 80x25 Apr 11 16:55:42 s1 kernel: Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes) Apr 11 16:55:42 s1 kernel: Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes) Apr 11 16:55:42 s1 kernel: Software IO TLB disabled Apr 11 16:55:42 s1 kernel: Memory: 2043384k/2097152k available (2513k kernel code, 53108k reserved, 1395k data, 184k init) Apr 11 16:55:42 s1 kernel: Calibrating delay using timer specific routine.. 5025.13 BogoMIPS (lpj=10050261) Apr 11 16:55:42 s1 kernel: Security Framework v1.0.0 initialized Apr 11 16:55:42 s1 kernel: SELinux: Initializing. Apr 11 16:55:42 s1 kernel: selinux_register_security: Registering secondary module capability Apr 11 16:55:42 s1 kernel: Capability LSM initialized as secondary Apr 11 16:55:42 s1 kernel: Mount-cache hash table entries: 256 Apr 11 16:55:42 s1 kernel: CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) Apr 11 16:55:42 s1 kernel: CPU: L2 Cache: 512K (64 bytes/line) Apr 11 16:55:42 s1 kernel: CPU: Physical Processor ID: 0 Apr 11 16:55:42 s1 kernel: CPU: Processor Core ID: 0 Apr 11 16:55:42 s1 kernel: (SMP-)alternatives turned off Apr 11 16:55:42 s1 kernel: Brought up 1 CPUs Apr 11 16:55:42 s1 kernel: checking if image is initramfs... it is Apr 11 16:55:42 s1 kernel: Grant table initialized Apr 11 16:55:42 s1 kernel: NET: Registered protocol family 16 Apr 11 16:55:42 s1 kernel: Brought up 1 CPUs Apr 11 16:55:42 s1 kernel: PCI: setting up Xen PCI frontend stub Apr 11 16:55:42 s1 kernel: ACPI: Interpreter disabled. Apr 11 16:55:42 s1 kernel: Linux Plug and Play Support v0.97 (c) Adam Belay Apr 11 16:55:42 s1 kernel: pnp: PnP ACPI: disabled Apr 11 16:55:42 s1 kernel: xen_mem: Initialising balloon driver. Apr 11 16:55:42 s1 kernel: usbcore: registered new driver usbfs Apr 11 16:55:42 s1 kernel: usbcore: registered new driver hub Apr 11 16:55:42 s1 kernel: PCI: System does not support PCI Apr 11 16:55:42 s1 kernel: PCI: System does not support PCI Apr 11 16:55:42 s1 kernel: NetLabel: Initializing Apr 11 16:55:42 s1 kernel: NetLabel: domain hash size = 128 Apr 11 16:55:42 s1 kernel: NetLabel: protocols = UNLABELED CIPSOv4 Apr 11 16:55:42 s1 kernel: NetLabel: unlabeled traffic allowed by default Apr 11 16:55:42 s1 kernel: NET: Registered protocol family 2 Apr 11 16:55:42 s1 kernel: IP route cache hash table entries: 65536 (order: 7, 524288 bytes) Apr 11 16:55:42 s1 kernel: TCP established hash table entries: 262144 (order: 10, 4194304 bytes) Apr 11 16:55:42 s1 kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) Apr 11 16:55:42 s1 kernel: TCP: Hash tables configured (established 262144 bind 65536) Apr 11 16:55:42 s1 kernel: TCP reno registered Apr 11 16:55:42 s1 kernel: audit: initializing netlink socket (disabled) Apr 11 16:55:42 s1 kernel: type=2000 audit(1365692095.507:1): initialized Apr 11 16:55:42 s1 kernel: VFS: Disk quotas dquot_6.5.1 Apr 11 16:55
