Troubleshooting a Freeze
Are there any general or specific tips on how to figure out what is causing FreeBSD to just freeze up? The machine is not at my physical location, and I log in using ssh. I've checked all the logs in /var/log for some kind of clue, but I haven't found anything helpful. The machine has worked fine for over 6 months, until the last few days it freezes up at apparently random times, normally within the first 12 hours of being up. While many ports have been added over the past 6 months, nothing was added on or around the time I started experiencing the problem. I guess I was wondering what some first steps people would take to troubleshoot an unexplained system hang. Some details: FreeBSD 4.8-RELEASE #0: Thu Apr 3 10:53:38 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz CPU: AMD Athlon(tm) XP 1800+ (1541.22-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x662 Stepping = 2 Features=0x383fbff AMD Features=0xc048 real memory = 536805376 (524224K bytes) avail memory = 517066752 (504948K bytes) open ports: ssh, smtp, imaps, pop3s, 8080 (http), https Thanks, Ryan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: how to make dhclient give up its lease and get a new one with routes, etc. ?
On Dec 9, 2003, at 1:33 PM, paul beard wrote: Advice on automagically notifying zoneedit is welcome, as well but not as pressing: I think they work with dyndns and of course I chose no-ip.org. I think you need to install /ports/dns/ddclient. This will update zoneedit when your IP is reassigned. -Ryan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: strange dump (dark matter?)
On Oct 22, 2003, at 5:26 PM, Ryan Sandridge wrote: On Oct 22, 2003, at 4:00 PM, Dave McCammon wrote: Where is the file of your first backup stored? Did it get backed up as part of the incremental backup? I should have mentioned that I had checked that already, because that would almost explain the unaccounted for 507 MB... but unless I'm missing something, that is not the problem. The backups were made onto /tmp filesystem, which were then archived to cd-rom, and deleted from /tmp. Ah, might be onto something though... I made an .iso file containing the dumps, which was copied to my home directory before burning to cd. That .iso file sat there until today, but was deleted before I did today's dump. So, I suppose it is possible that the filesystem wasn't flushed (is that what its called?), so the file was still there. I presume, however, this would be a bug with dump, as that .iso file is NOT in the archive. Do you think this is what happened? Thanks, Ryan Well, as a newbie, it only took me about 10 hours to figure out on my own that I needed to run fsck. It showed me that I had an unreferenced file hiding on my disk; however fsck never seemed to work as documented. I couldn't ever run it with 'fsck -p', I always received (and still do receive): /dev/ad0s1g: NO WRITE ACCESS /dev/ad0s1g: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. and when I ran it with just 'fsck', it would always answer "no" to the prompts to fix the problems without giving me an opportunity to fix it. No I didn't use the -n flag to force no responses, and I am aware of the -y flag, but the documentation warns against doing this. Finally I threw my hands up, and rebooted, which seemed to clear up the unreferenced file. -Ryan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: strange dump (dark matter?)
On Oct 22, 2003, at 4:00 PM, Dave McCammon wrote: --- Ryan Sandridge <[EMAIL PROTECTED]> wrote: Hello all. I decided it was time to start doing backups. On Oct 7th, I did a full dump of /usr filesystem (among others), as such: # dump -0uan -f - /usr | gzip -7 > /tmp/20031007-usr-lvl0.dump.gz This seemed to work as expected, here is some info about the gz file: % gzip -l 20031007-usr-lvl0.dump.gz compressed uncompr. ratio uncompressed_name 507027476 1590855680 68.1% 20031007-usr-lvl0.dump Everything so far so good. Today (Oct 22) I tried an incremental dump, as such: # dump -5uan -f - /usr | gzip -7 > /tmp/20031022-usr-lvl5.dump.gz Here is where I start getting confused. While my other incremental backups today (/ and /var), seemed to be fine, the /usr dump was huge. Here is info about the gz file: % gzip -l 20031022-usr-lvl5.dump.gz compressed uncompr. ratio uncompressed_name 527112624 543600640 3.0% 20031022-usr-lvl5.dump This incremental backup is larger than the original full dump. Also notice that the compression ratio was 3.0%. When examining the list of files dumped, I don't see anything that could lead to a file size like this. A rough count shows that the backup should have been roughly 11MB uncompressed, compared to the 518MB uncompressed. I've tried reading up on both dump and gzip, but haven't found a clue. Perhaps I've discovered dark matter. Thanks, Ryan Where is the file of your first backup stored? Did it get backed up as part of the incremental backup? I should have mentioned that I had checked that already, because that would almost explain the unaccounted for 507 MB... but unless I'm missing something, that is not the problem. The backups were made onto /tmp filesystem, which were then archived to cd-rom, and deleted from /tmp. Ah, might be onto something though... I made an .iso file containing the dumps, which was copied to my home directory before burning to cd. That .iso file sat there until today, but was deleted before I did today's dump. So, I suppose it is possible that the filesystem wasn't flushed (is that what its called?), so the file was still there. I presume, however, this would be a bug with dump, as that .iso file is NOT in the archive. Do you think this is what happened? Thanks, Ryan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
strange dump (dark matter?)
Hello all. I decided it was time to start doing backups. On Oct 7th, I did a full dump of /usr filesystem (among others), as such: # dump -0uan -f - /usr | gzip -7 > /tmp/20031007-usr-lvl0.dump.gz This seemed to work as expected, here is some info about the gz file: % gzip -l 20031007-usr-lvl0.dump.gz compressed uncompr. ratio uncompressed_name 507027476 1590855680 68.1% 20031007-usr-lvl0.dump Everything so far so good. Today (Oct 22) I tried an incremental dump, as such: # dump -5uan -f - /usr | gzip -7 > /tmp/20031022-usr-lvl5.dump.gz Here is where I start getting confused. While my other incremental backups today (/ and /var), seemed to be fine, the /usr dump was huge. Here is info about the gz file: % gzip -l 20031022-usr-lvl5.dump.gz compressed uncompr. ratio uncompressed_name 527112624 543600640 3.0% 20031022-usr-lvl5.dump This incremental backup is larger than the original full dump. Also notice that the compression ratio was 3.0%. When examining the list of files dumped, I don't see anything that could lead to a file size like this. A rough count shows that the backup should have been roughly 11MB uncompressed, compared to the 518MB uncompressed. I've tried reading up on both dump and gzip, but haven't found a clue. Perhaps I've discovered dark matter. Thanks, Ryan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Configuring imap-uw difficulties
On Monday, Sep 29, 2003, at 13:16 US/Eastern, Charles Swiger wrote: On Monday, September 29, 2003, at 01:10 PM, Ryan Sandridge wrote: My trouble is with changing some of the defaults. Unless I'm missing something, all configuration is done through re-compiling rather than a configuration file. Not my preference, but I can deal with that. In particular I modify .../src/osdep/unix/env_unix.c to change the mail subdirectory name. I thought after making this change, all I needed to do was '$ cd /usr/ports/mail/imap-uw' then type '$ make' to rebuild it with the changes. But it seems to think it is up to date (so doesn't recompile). So perhaps my confusion is really due to lack of understanding of the Ports system or of how to compile. You should try the following: cd /usr/ports/mail/imap-uw make clean make deinstall make patch [ ...change the env_unix.c file under the work subdir... ] make make install Thanks for the lightening fast response. This compiled as expected, although my source change did not appear to take effect. After changing the mailsubdir from NIL to "mail", I'm still dumped in my home directory, not mail subdirectory. This is probably an issue I should take up with the imap-uw mailing list. I do have a followup question to your response. Doing 'make clean' removes everything in the work subdir, right? So if I follow all those steps every time I want to make a change, won't I need to make all previous changes again? Is there a better way? Thanks, Ryan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Configuring imap-uw difficulties
This is my first post so go easy on me :-) I'm relatively new to the FreeBSD world, but I've seen enough to favor using the Ports collection over any other method. I am running 4.8-RELEASE #0. I installed /usr/ports/mail/imap-uw using 'make install'. After much confusion with OpenSSL, I finally got it working (correctly I think) with all the defaults. Oh, imap-uw version is 2002d,1. My trouble is with changing some of the defaults. Unless I'm missing something, all configuration is done through re-compiling rather than a configuration file. Not my preference, but I can deal with that. In particular I modify .../src/osdep/unix/env_unix.c to change the mail subdirectory name. I thought after making this change, all I needed to do was '$ cd /usr/ports/mail/imap-uw' then type '$ make' to rebuild it with the changes. But it seems to think it is up to date (so doesn't recompile). So perhaps my confusion is really due to lack of understanding of the Ports system or of how to compile. Thanks, Ryan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
