Starwind HA logging

Software-based VM-centric and flash-friendly VM storage + free version

Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)

Post Reply
TomHelp4IT
Posts: 22
Joined: Wed Jul 29, 2009 9:03 pm

Wed Dec 09, 2009 3:48 pm

I've had our test HA cluster running for over a month now, its been over 3 weeks since either of the nodes was restarted and everything is still looking fine so far which is good. One thing I have noticed though is that after a week or so the Starwind console can no longer display the logfile as its too big, so I have to open the file manually to check it. Apart from all the logging for mounting the targets and initiators connecting at the start, afterwards all the entries are like this:

12/9 15:29:32.372 14a4 HA: HA_ScsiCommandCreateObject: EXITing with success (*p_ppSscObject = 0x0230B344)
12/9 15:29:32.372 14a4 HA: HA_ScsiCommandCreateObject: EXITing with success (*p_ppSscObject = 0x0230B344)
12/9 15:29:32.388 14a4 HA: HA_ScsiCommandCreateObject: EXITing with success (*p_ppSscObject = 0x0230B344)
12/9 15:29:32.388 14a4 HA: HA_ScsiCommandCreateObject: EXITing with success (*p_ppSscObject = 0x0230B344)

These will occur at least every 5 minutes, and I guess they are not a problem since it says "success", but it does concern me a bit as to how large the logfile could get since its already reached 50MB. Is there any way to reduce the logging level so these arent included but the important stuff is, or to get it to rotate logs every 10MB or something? Apart from anything else it is rather inconvenient having to go and open the log manually after you went and put that nice viewer into the new console.

Thanks
User avatar
Aitor_Ibarra
Posts: 163
Joined: Wed Nov 05, 2008 1:22 pm
Location: London

Thu Dec 10, 2009 5:40 am

Hi Tom,

In Starwind 4.1 (at least) there was setting in the config file:

<LogLevel value="1"/> - I think higher means more verbose. I've not checked whether SW5 has the same setting yet as I've yet to put it into production (have upgraded my license but am waiting for a new build which I'm hoping will fix an issue I found), but logging verbosity should really be settable in the UI, IMHO.

I had a problem where the logs would eventually fill up my boot volume (I had a very small boot volume). In the end I just set the log directory to be compressed, which buys you a lot of time...

hope this helps,

Aitor
Constantin (staff)

Fri Jan 15, 2010 1:35 pm

LogLevel=1 is default status. To turn logs off it should be changed to 0. This message is synch status.
Post Reply