openBSD 3.5 sm-msp-queue error ?
 

2 months ago I installed and set up openBSD 3.5 to use for firewall/routing of my local network. I am new to the universe of *nix/BSD and am learning as I go. I've searched the forums and googled for various words in this error, and have found nothing to even put me on the right track to fix the problem. I can just reinstall, but I would rather learn how to fix this problem correctly if possible.

I live in florida, and the recent hurricane left me without power for 10 days. I shutdown all my systems before the storm, but forgot about the openBSD box, because of it's infrequent use. It was on a UPS, but 10 days was a bit much to ask of it. The system was obviously shutdown incorrectly. Now that I have power back, the box will lockup/reboot every 8 hours.

30 minutes after boot, and repeated every 30 minutes after that I get this message across the console, which I assume is being posted to a log somewhere. If this logfile will help in diagnosis, please let me know where to find it, and I can post it for you. The message is :

<Date> <time> <machinename> sm-msp-queue[2702]: i7IL01qY018566: SYSERR(root): readqf: ./qfi7IL01qY018566: incomplete queue file read

The only services I have set up to run are pf, and dhcpd. I have not turned off/on any other services from the default 3.5 install. Please let me know if there are any logs, or information I can provide to aide you. Thank you for your time.

That's Sendmail. It looks like it has a message stuck that got partially queued. Best thing would be to manually clean out the Sendmail queue by rm'ing the file specified above (qfi7IL01qY018566).

Thank you for your help chort. What dir should I start looking for the file?

Thanks for your time,

smurfzilla

Is there a command similar to grep that searches for files themselves, rather then inside files ? I'm currently trying to use ls, but can't figure out how to wild card it.

-smurf

**edit
with a little searching here, i found the find cmd, which let me find the location of the file. Thanks for your help chort, and I'll let you know if rm'ing the file fixes my problem.

After finding and rm'ing the offending file. All seemed well for awhile. I no longer get the sm-msp-queue error, but I now am getting random lockups. The time used be 8 hours before lockup, now it is seemingly random intervals. The shortest being 20 min. Any idea where to look for problems?

Problem is solved. After a failed reinstall, I tried another hd. The reinstall also failed. I replaced the ram, and reinstalled on the original drive and all is well. So far the box has been up for 1 day.

-smurf