First of all, I would like to give a particular thanks to: John Hilger, Dietmar Swoboda, Keith Jenkinson, Wallace MA Jeffrey Lai, Andy Scutt, and Thorsten Clever... ...thanks for having replied *automatically* to my message that you were in vacation: that helped me a LOT! ;-) Seriously, I would like to thank, in the first place, Neezam Haniff, who pointed to me that I wasn't using "vmstat" correctly. Mr. "darrenprog" did it as well... I had to let it go more longer to see the *real* stats. In fact, the first output, when usint "vmstat" without arguments, gives an average since the system was rebooted... ...not that usefull in my case! So, I took a bit of humility (ahem!) and did back my homeworks and found that I was short in memory usage on the system... Ok, I know, I know, it was pretty clearly mentionned in the log files, but I wasn't suspecting it to be a *real* memory problem... ...common, NTP shouldn't need that much memory, isn't? But I tried it back this morning, with a little more memory left on the system, and guess what? It passed perfectly. So, this was clearly a memory issue. Once again, thanks! Following is my original post... Hi fellow managers, I have a Solaris 8 running a Oracle 8i database, and that was running xntpd without a problem. I had to change the NTP servers today and everything went fine on other servers, except this one. As soon as I restart the xntpd daemon, these entries are logged in "/var/adm/messages": Sep 13 13:16:35 uprb01 ntpdate[24966]: [ID 558275 daemon.notice] adjust time server 172.26.2.34 offset 0.125731 sec Sep 13 13:16:35 uprb01 ntpdate[24966]: [ID 558275 daemon.notice] adjust time server 172.26.2.34 offset 0.125731 sec Sep 13 13:16:37 uprb01 xntpd[24968]: [ID 702911 daemon.notice] xntpd 3-5.93e Mon Sep 20 15:47:11 PDT 1999 (1) Sep 13 13:16:37 uprb01 xntpd[24968]: [ID 702911 daemon.notice] xntpd 3-5.93e Mon Sep 20 15:47:11 PDT 1999 (1) Sep 13 13:16:37 uprb01 xntpd[24968]: [ID 904279 daemon.error] mlockall(): Resource temporarily unavailable Sep 13 13:16:37 uprb01 xntpd[24968]: [ID 904279 daemon.error] mlockall(): Resource temporarily unavailable Sep 13 13:16:37 uprb01 xntpd[24968]: [ID 220665 daemon.error] No more memory! Sep 13 13:16:37 uprb01 xntpd[24968]: [ID 220665 daemon.error] No more memory! Of course, the daemon is not running after occurrence of these log entries... I double checked the config files (/etc/inet/ntp.conf), I put back the old one, checked on other servers and everything seems to be ok. However, I looked at the memory usage on the server, with "vmstat", and I got this: server-name# vmstat procs memory page disk faults cpu r b w swap free re mf pi po fr de sr m0 m1 m2 m3 in sy cs us sy id 0 0 1 4722144 984656 0 0 0 0 0 0 0 5 4 4 0 4294967196 0 0 -4 -3 -141 Is this normal the negative values in the "cpu" columns? I never saw that before... I browsed the web for something, by found nothing really relevant... ...only one person who had this problem in july 2002, but no summary was posted back. This obvious that I'll post a summary, as soon as I get it fixed!! ;-) Thanks in advance and have a nice day. _______________________________________________________________ Benoit Audet Conseiller - TELUS solutions d'affaires Commission administrative des rigimes de retraite et d'assurances (CARRA) Service de l'assistance et des technologies (SAT) Til : 418.528.1303 (CARRA) benoit.audet@carra.gouv.qc.ca benoit.audet@telussa.com _______________________________________________________________ _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagersReceived on Tue Sep 14 08:38:45 2004
This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:43:37 EST