Jump to content
Division-M Community
Bigrizz

What is db-startup.sil in the logs folder? Why's DB smashing my CPU?

Recommended Posts

Last night, the ssd system drive on my HP Microserver ran out of room. Windirstat revealed a file called 'db-startup.sil' in the logs folder that was 18.4GB. Bizarrely, after rebooting last night, it's gone today. Anyone know what it is?

 

DB consistently chews at least 30-40% of my CPU and even more after a startup. Are the events related? Anyone else experiencing high CPU usage?

 

I have 4 drives in my pool, two 1.5TB and two 2TB drives.

Share this post


Link to post
Share on other sites

It's the log file for Drive Bender.

 

It should never get that big as I thought it got recycled at 1Mb in size.

 

If you see it growing again, raise a Support Ticket.

Share this post


Link to post
Share on other sites

It's the log file for Drive Bender.

 

It should never get that big as I thought it got recycled at 1Mb in size.

 

If you see it growing again, raise a Support Ticket.

 

Thank you. In the event it gets huge again, is it safe to delete it until a support ticket is raised and dealt with?

Share this post


Link to post
Share on other sites

I'd still raise a Support Ticket.

Yep, understand that. If it takes days to resolve, my server will be offline for that time if I can't delete the file. The question was is it safe to delete the file?

Share this post


Link to post
Share on other sites

Yes, it's perfectly safe to delete the .sil files. They are simply logs. Just curious what your logging level is set to. This can be found in DB settings on the Performance tab. Normally this should be set to None unless you are directed by DB support to set it to a particular logging level.

Share this post


Link to post
Share on other sites

Yes, it's perfectly safe to delete the .sil files. They are simply logs. Just curious what your logging level is set to. This can be found in DB settings on the Performance tab. Normally this should be set to None unless you are directed by DB support to set it to a particular logging level.

Yes, set to none.

Share this post


Link to post
Share on other sites

Last night, the ssd system drive on my HP Microserver ran out of room. Windirstat revealed a file called 'db-startup.sil' in the logs folder that was 18.4GB. Bizarrely, after rebooting last night, it's gone today. Anyone know what it is?

 

DB consistently chews at least 30-40% of my CPU and even more after a startup. Are the events related? Anyone else experiencing high CPU usage?

 

I have 4 drives in my pool, two 1.5TB and two 2TB drives.

 

Well also here. DB will use 30-40% of my CPU (v.2.3.8.0). but in the Moment i restore 3 TB home videos and DB is balancing in the background.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...