[Moabusers] MOAB Not Starting

[Austin Godber]

Aaaah, swell.  Software licensing is an evil waste of time and the main
reason I try to stick to FOSS.

root at colossus:/opt/moab# /usr/local/sbin/moab -d
NOTE:  Moab Workload Manager evaluation period has expired.
       Please contact Cluster Resources, Inc. for assistance.
       (email: sales at clusterresources.com/phone: +1 801 798 7520)

I have a license file.  I placed it in /opt/moab/moab.lic where moab is
located.  Its valid:

# Generated on Thu May  4 11:17:23 2006
# Valid on host 'colossus'
# Valid up to 240 processors
# Expires after Sun Jul  8 11:17:23 2007

I wonder if for some reason it doesn't work with the moab version I
installed.  The guy who game me my license sent me the wrong Moab
tarball so I just installed one that I had downloaded.  Must have been a
demo.

Any clue?

Austin

wightman wrote:
> If you change the following:
> 
> SCHEDCFG[] MODE=TEST
> 
> Then you can run Moab and Maui side by side.  Moab will pretend it is
> scheduling but it won't actually start/cancel/preempt any jobs (it's
> basically a read-only mode).
> 
> You should be able to test Moab while Maui is running.
> 
> - Douglas
> 
> On Thu, 2006-09-14 at 10:08 -0700, Austin Godber wrote:
>> Oh, -d maybe that would help.  Thanks.  I can't try it at the moment
>> since I have reverted to my old Maui installation so people could use
>> the cluster.
>>
>> I did an strace a few times and each time it ended with (near the end)
>> setsid returning an error.  I don't know if thats related or not.
>>
>> I will try with -d if I can sneak it in today.
>>
>> Austin
>>
>> wightman wrote:
>>> Can you tell if Moab is crashing or receiving a signal of any kind?
>>>
>>> Try starting moab with the -d flag.  This will stop Moab from
>>> backgrounding itself and may print out some more information.
>>>
>>> - Douglas
>>>
>>> On Wed, 2006-09-13 at 15:54 -0700, Austin Godber wrote:
>>>> I have Moab 4.5.0p3 with torque 2.11 as the RM and MOAB will not
>>>> continue running when started.  It runs for a few seconds, schedules a
>>>> few jobs and then exits.  The only log info I get with the default
>>>> logging is:
>>>>   09/13 15:47:18 WARNING:  cannot record MONTH stats
>>>> Increasing the log level a few doesn't reveal anything unsavory.  There
>>>> have not been any recent changes to any of the components in the last
>>>> month or so.
>>>>
>>>> When it dies it leaves a pid file and ck file.
>>>>
>>>> Any pointers on getting this started?  Maybe if I nuke all the queued
>>>> jobs in torque and start fresh?
>>>>
>>>> Austin
>>>> _______________________________________________
>>>> moabusers mailing list
>>>> moabusers at supercluster.org
>>>> http://www.supercluster.org/mailman/listinfo/moabusers
>