Greetings,
I have been testing the new pulldata option in the snapshot from June 29, 2006, however I have run into a problem. Basically, hobbit has decided to not pull data from 2 of my 5 clients that I am testing this on. This is in a trucluster 5 environment and its cluster mate is also having the same problems.
When I installed I made sure to completely wipe out the client directory (just in case - plus I had not made any customizations). I am not sure where to look because I have look through the logs and can't find anything referencing this host. Any ideas??
Thanks,
Adam
I had 4.1.1 running fine and wanted to move to the latest beta release. The compile seemed to go fine, but the hobbit log shows this now:
2006-06-29 22:16:33 Could not get shm of size 262144: Invalid argument 2006-06-29 22:16:33 Cannot setup status channel 2006-06-29 22:16:33 Task hobbitd terminated, status 1
I have plenty of shared memory I am almost sure and the other channel problem I should not have either. Here is my system file:
set shmsys:shminfo_shmmax=16000000 set shmsys:shminfo_shmmin=1 set shmsys:shminfo_shmmni=100 set shmsys:shminfo_shmseg=20 set semsys:seminfo_semmns=400 set semsys:seminfo_semmni=140 set semsys:seminfo_semmsl=60
This is Solaris 8 btw. Any ideas?
Thanks
Wes Neal wrote:
I had 4.1.1 running fine and wanted to move to the latest beta release. The compile seemed to go fine, but the hobbit log shows this now:
2006-06-29 22:16:33 Could not get shm of size 262144: Invalid argument 2006-06-29 22:16:33 Cannot setup status channel 2006-06-29 22:16:33 Task hobbitd terminated, status 1
I have plenty of shared memory I am almost sure and the other channel problem I should not have either. Here is my system file:
set shmsys:shminfo_shmmax=16000000 set shmsys:shminfo_shmmin=1 set shmsys:shminfo_shmmni=100 set shmsys:shminfo_shmseg=20 set semsys:seminfo_semmns=400 set semsys:seminfo_semmni=140 set semsys:seminfo_semmsl=60
This is Solaris 8 btw. Any ideas?
Did you reboot after editing /etc/system? Unlike Linux, Solaris must be rebooted for the changes to take effect -
J
I didn't make any changes to /etc/system this time, my system file has been that way since I first moved from BB to Hobbit. Any other ideas?
-----Original Message----- From: J Sloan [mailto:joe at tmsusa.com] Sent: Friday, June 30, 2006 2:00 AM To: hobbit at hswn.dk Subject: Re: [hobbit] Problem with the latest release
Wes Neal wrote:
I had 4.1.1 running fine and wanted to move to the latest beta release. The compile seemed to go fine, but the hobbit log shows this now:
2006-06-29 22:16:33 Could not get shm of size 262144: Invalid argument 2006-06-29 22:16:33 Cannot setup status channel 2006-06-29 22:16:33 Task hobbitd terminated, status 1
I have plenty of shared memory I am almost sure and the other channel problem I should not have either. Here is my system file:
set shmsys:shminfo_shmmax=16000000 set shmsys:shminfo_shmmin=1 set shmsys:shminfo_shmmni=100 set shmsys:shminfo_shmseg=20 set semsys:seminfo_semmns=400 set semsys:seminfo_semmni=140 set semsys:seminfo_semmsl=60
This is Solaris 8 btw. Any ideas?
Did you reboot after editing /etc/system? Unlike Linux, Solaris must be rebooted for the changes to take effect -
J
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
Anyone else with any ideas?
From: Wes Neal [mailto:wes.neal at verizonbusiness.com] Sent: Thursday, June 29, 2006 11:23 PM To: hobbit at hswn.dk Subject: [hobbit] Problem with the latest release
I had 4.1.1 running fine and wanted to move to the latest beta release. The compile seemed to go fine, but the hobbit log shows this now:
2006-06-29 22:16:33 Could not get shm of size 262144: Invalid argument 2006-06-29 22:16:33 Cannot setup status channel 2006-06-29 22:16:33 Task hobbitd terminated, status 1
I have plenty of shared memory I am almost sure and the other channel problem I should not have either. Here is my system file:
set shmsys:shminfo_shmmax=16000000 set shmsys:shminfo_shmmin=1 set shmsys:shminfo_shmmni=100 set shmsys:shminfo_shmseg=20 set semsys:seminfo_semmns=400 set semsys:seminfo_semmni=140 set semsys:seminfo_semmsl=60
This is Solaris 8 btw. Any ideas?
Thanks
participants (3)
-
adam.scheblein＠marquette.edu
-
joe＠tmsusa.com
-
wes.neal＠verizonbusiness.com