NASLite Network Attached Storage

Is there a way to save a log file and not rewrite it with the CDD version? I have had a couple spontaneous shutdowns and connection issues lately and I am trying to determine what the problem is but the log file is overwritten each time on boot and therefore I can't see what it says as to what caused the issue. So is there a setting or something that will archive the log before writing a new on on boot?

Thanks,

Lance

The best I can figure, no! Naslite is stateless and on reboot everything is newly created with nothing left from the previous run. If you are getting random reboots, then I'd take a very good look at the IRQs things use. I had a machine doing that on occasion. Turned out to be a chatty RTL NIC that was not pulling it's weight. An Intel pro took care of that little issue.

Thanks, an Intel pro NIC is a good card to use? I'm using the onboard nic and I do get some issues when transferring large files over (path too deep errors when copying multiple files > 1GB each) and it locks down the whole machine requiring a reboot and a check of the file system. Has happened when I had other HDDs in and when I replaced all HDDs with a 1.5TB array as well...

Perhaps I'll try to pick up a Intel Pro NIC. Anything I need to look out for when looking for one? not used a NIC card in quite a while other than MB ones.

not knocking current status of NL at all, it works very well for me thank you!

But sending syslog data to a syslog server would be nice

Or even snmp data that one could probe....

But if it crashed that hard I suppose I would see any good stuff anyway...

How many people have a syslog server running in their house?

oh i understand, but it might fit in there mounting remote shares between naslite and other machines that can use it..

the feature is there, but how many folks really use it?? Are the ones that would use this feature the same class that would use syslog?? How about rsync?

There are free ones, http://tftpd32.jounin.net

I just wrote a java program that will go out to the log and download it off the web page every so often so I can save it on my local machine. It would be nice if it would write somewhere and be arhived for say one revision so when you recover you can find out what might have happened.

Although I think i'm going to go buy a new MB and stuff for my server as it seems to be hanging more consistantly now and see if maybe that helps things. I've replaced all HDDs and cables so I don't think it is those. Hopefully I can just get some new "old" hardware and build another server and go that route.

Anyone have suggestions for MB, CPU and stuff for building a new one that won't lag?

Lance

Before rebuilding the whole thing, try a single stick of different memory, reset the BIOS to safe defaults and give it one last try.

Well I've run MemTest86 on it several times with no problems. I'm thinking it's time to just rebuild as I need to to be pretty solid as it serves as my main file server and when it's down, i'm down and can't get to my files. Anyone have any thoughts on some good cheap hardware that will work with the software?

Lance

http://www.newegg.com/Product/Product.a ... 6813185043

I have about 30 of these boards running Naslite at various customer locations and none have had problems as of yet. It has been over 2 years since the first one. The only problem is no on-board SATA, but that's ok, plenty of SATA PCI cards out there.

Thanks, I'll check it out. I have an 8 IDE 3Ware Raid card I use anyway so onboard SATA isn't really all that necessary for me.

Lance

*raises hand*

I think having the option to log to an external syslog server would be a very useful feature for future versions of NASlite-2.

My point was the average Joe will not need remote logging.

This thread full of average Joes is singing a different tune

Anyway, this is a very simple feature to add, one line in /etc/syslog.conf and it's done.