**** BEGIN LOGGING AT Sun Mar 05 10:59:56 2006 Mar 05 11:08:38 goodmorning Mar 05 11:08:59 caplink811_log: you are right with every 20 minutes Mar 05 11:09:28 a time update.. because when you set it to 3 hours it wil not work Mar 05 11:52:28 new idea :) someone try to email the /var/log/message from the last day to your email adress ? Mar 05 12:57:53 mika_, try syslog-ng which have additional features Mar 05 13:01:33 thx caplink811_log i wil see it after i have eat.. Mar 05 13:36:27 caplink811_log: there are some problems with syslog-ng as i read : http://www.nslu2-linux.org/wiki/HowTo/InstallAndConfigureSyslog-ng Mar 05 13:39:23 i think i gona write a small script with this http://www.nslu2-linux.org/wiki/HowTo/UseSmtpClient Mar 05 13:46:58 hmmm :S But as I said not all options work in this build. Mar 05 13:47:09 the option -S works not ... Mar 05 14:31:57 caplink811_log: this part is working no build a script that send only from the last day Mar 05 14:32:01 cat /var/log/messages | smtpclient -v -s "log from nslu2" xxxx@gmail.com -f xxxx@gmail.com Mar 05 18:05:41 my nslu2 seems to have developed a nasty habit of crashing hard after it's been running for a few hours. Mar 05 18:06:31 by 'crashing hard' i mean no response to network traffic, or me pushing the power button. the only way out is to pull the PSU out and replug it Mar 05 18:06:48 nothing at all in /var/log/*, it just stops dead Mar 05 18:07:11 philpem: any chance you are running openntpd ? Mar 05 18:10:55 nope Mar 05 18:11:37 too bad, i had similar problems last week (hard lock up every 10 hours) and it was solved after a clean install, but never reinstalled openntpd Mar 05 18:11:38 the slug itself has had a poweron hack and the turboslug (233MHz clock unlock) mods applied, and is running OpenDebianSlug, i.e. debian armeb. Mar 05 18:12:01 i had that problem with both DebianSlug and OpenDebianSlug Mar 05 18:12:07 oh wonderful Mar 05 18:12:10 it is turboed Mar 05 18:12:19 but no the poweron hack Mar 05 18:13:27 nice to know i'm not the only person who's had this happen, but i'd still like to know what's causing it... Mar 05 18:13:52 yes, i was really feeling lonely with it ;) Mar 05 18:14:07 but i do blame it on openntpd Mar 05 18:14:13 or... Mar 05 18:14:19 as far as software goes, it's the base opendebianslug with eciadsl, fetchmail, postfix and dovecot installed. no nntp daemons at all Mar 05 18:14:23 what kernel are you running? Mar 05 18:14:58 Linux wolf.philpem.me.uk 2.6.12.2 #1 Tue Sep 27 20:21:18 CDT 2005 armv5teb GNU/Linux Mar 05 18:15:01 my last install was with the kernel released last sunday (i.e. 2.6.16-rc4-git5) Mar 05 18:16:04 had the problem with self-build debianslug, kernel 2.6.15 and opendebianslug, same kernel as you Mar 05 18:16:38 running slapd, samba, krb5-kdc, mt-daapd Mar 05 18:16:54 bind9, dhcp3-server Mar 05 18:16:59 and some other minor stuff Mar 05 18:17:24 so you're currently running the 2.6.16 kernel? Mar 05 18:17:36 yes, not the latest though Mar 05 18:18:00 i have a newer image built but not gotting around to install it yet Mar 05 18:19:53 but it can hardly be the kernel because than more people would experience the same Mar 05 18:20:17 i assume you use the openslug 2.7 image? Mar 05 18:20:25 yup Mar 05 18:29:06 any pattern in the locks? interval? Mar 05 18:29:19 not as far as i can tell Mar 05 18:29:23 i had mine happening somewhere between 9 and 10 hours after boot Mar 05 18:29:32 (not really poweron) Mar 05 18:29:35 there's nothing in syslog, the machine just stops dead after about 9 hours Mar 05 18:29:50 well, sounds *very* similar Mar 05 18:30:18 maybe it was not openntpd after all Mar 05 18:30:25 but a kernel issue Mar 05 18:30:34 how long have you had your slug? Mar 05 18:30:55 abut two days Mar 05 18:31:12 i bought mine about three weeks ago Mar 05 18:31:24 then one week went with fooling around Mar 05 18:31:37 and then just as i thought i ad a stable installation Mar 05 18:31:51 it started doing the '10 hour freeze' thing Mar 05 18:32:02 that lasted for a week Mar 05 18:32:17 but the last week the system has only rebooted when i asked it to ;) Mar 05 18:32:46 it is an anoying problem, since you don't know a thing until it happens Mar 05 18:32:50 yeah Mar 05 18:33:17 maybe you should try to build an more recent openslug kernel Mar 05 18:33:21 i might set up a 5-minute cron that appends the uptime to a file in /tmp Mar 05 18:33:46 that should tell me roughly when the crashes are occuring and might help pin down what's happening Mar 05 18:33:47 but mind you, the first build is a very lengthy process Mar 05 18:34:27 i've got 2.7 building... might try grabbing a later version. Mar 05 18:34:53 let it build Mar 05 18:35:07 and replace the kernel with a newer one (most recent?) afterwards Mar 05 18:35:26 what i meant to say was "i've got 2.7 built, and sources on my laptop" Mar 05 18:35:45 did that to get some more kernel modules built (n_hdlc + a few others) Mar 05 18:36:01 ah, k Mar 05 18:36:34 well, would be interesting to see wht happens when you build the latest openslug Mar 05 18:37:02 i'm testing it in ram first though :P Mar 05 18:37:06 i did not build openslug, but debianslug since the problem was occuring in both Mar 05 18:37:28 and the package repository for debianslug is so much more extensive Mar 05 18:39:25 i'm running opendebianslug, i.e. openslug kernel with debian big-endian packages Mar 05 18:39:51 yes, i know (and we agree upon ;) the terminology Mar 05 18:40:29 i initially thought the problem had to do with the LE/BE hack for the IXP400 interface Mar 05 18:40:59 so i was quite suprised when +/- 9 hours after boot of opendebianslug the system locked up again Mar 05 18:41:05 it looks to me like the kernel is panicking, but i don't have a serial console cable to check :-/ Mar 05 18:41:07 (and frustrated) Mar 05 18:41:15 yeah, same here Mar 05 18:41:38 that was on the list... but it dissappeared after a fresh build of debianslug last sunday Mar 05 18:45:02 think i'll probably build a serial cable at some point... i figure i've voided the warranty irrevocably now, so a little more can't really hurt :) Mar 05 19:24:59 I believe that netconsole builds for openslug; perhaps that might help with the possible panic in the absence of a serial port? Mar 05 19:25:27 might yes Mar 05 19:25:39 but i tried, and it does not report anything either Mar 05 19:25:52 only surefire way is to use an actual serial console Mar 05 19:38:51 I most certainly agree; one of my slugs has a serial cable and I feel like a blind man who suddenly gained back his sight... :) Mar 05 19:39:44 capbot: greetings! Mar 05 19:40:34 * mwester decides that that is not the way to get the bot to say anything... Mar 05 19:41:12 ~snacks Mar 05 19:41:24 hm Mar 05 19:41:29 !help Mar 05 19:41:29 ->> Type: !mika ?| !lastseen | !lastspoke | !seen | !mika version Mar 05 19:41:32 ~help Mar 05 19:41:36 °help Mar 05 19:41:56 A most recalcitrant bot, no? Mar 05 19:42:20 ~uptime Mar 05 19:42:48 ~cookie Mar 05 19:42:50 * capbot pulls out the cookie jar and finds nslu2-info... at http://www.nslu2-info.de Mar 05 19:43:05 Behold! It speaks! :D Mar 05 19:43:06 :-) Mar 05 19:43:21 ~freshmeat Mar 05 19:43:38 hm Mar 05 19:45:35 ~freshvegetables Mar 05 19:45:48 * mwester thinks perhaps the bot is vegetarian... Mar 05 19:45:58 capbot hi Mar 05 19:45:59 que tal, caplink811_log Mar 05 19:46:29 ~tell Eiffel_ about help Mar 05 19:47:44 ~botsnack Mar 05 19:47:45 aw, gee, caplink811_log Mar 05 19:47:46 it is Mar 05 19:48:08 he only like snacks, no meat, and no vegetables ;) Mar 05 20:12:52 mwester: thanks for the suggestion, just setting up netconsole now :) Mar 05 20:20:46 hmm, not working Mar 05 20:31:29 ... because sysklogd and klogd were running... Mar 05 20:49:09 that should not matter, philpem Mar 05 20:50:53 netconsole can run alongside sysklogd/klogd or syslog-ng Mar 05 21:03:07 well i didn't get any messages on kiwi syslog (or any syslog packets going out of the nslu) until i stopped klogd Mar 05 21:13:30 hmmmm Mar 05 21:13:49 maybe that is why my panic dump failed Mar 05 21:13:59 but i did get some info from netconsole Mar 05 21:14:14 must have been mislead then Mar 05 21:47:29 this is interesting: http://groups.yahoo.com/group/nslu2-linux/message/8781 Mar 05 21:47:42 "i overclocked my slug, now it crashes" Mar 05 22:11:24 ok, the "inferior chips" theory is crap. according to intel, those chips will do 266. Mar 05 22:12:20 and as far as cooling goes, castle's iyonix does 600MHz core on an xscale quite happily, and there's no heatsink on the cpu... that said, the case is a hell of a lot bigger :) Mar 05 22:14:03 i will, however, install kiwi syslog on my laptop and set it logging overnight. Mar 05 22:16:37 hello, anyone accessing their slug using a Pocket PC ? Mar 05 22:17:14 Flipo_, yes, i am using pocketputty to log into the slug shell and streaming music from mtdaapd to WiFiTunes Mar 05 22:18:48 Ok, I can't access my slug using the R63 firmware (probably because they updated samba) and was wondering if it would be similar in unslung6... Mar 05 22:19:07 that's when I use my pocket pc, other devices can access the slug Mar 05 22:21:05 I assume you are running version 5.5 ? Mar 05 22:21:24 Flipo_, yup, unslung 5.5 beta all the way here Mar 05 22:22:28 my pocket pc could access the slug when I was running 5.5 but I guess it might not work with 6 since it's based on R63 Mar 05 22:24:18 Flipo_, thanks for the warning about trying unslung 6 beta :-P Mar 05 22:24:18 Linux kfm82slug 2.4.22-xfs #1 Sun Jun 12 21:17:17 PDT 2005 armv5b unknown Mar 05 22:24:18 kfm82slug:~/config root# uname -a Mar 05 22:24:18 Linux kfm82slug 2.4.22-xfs #1 Sun Jun 12 21:17:17 PDT 2005 armv5b unknown Mar 05 22:24:18 kfm82slug:~/config root# uname -a Mar 05 22:24:21 Linux kfm82slug 2.4.22-xfs #1 Sun Jun 12 21:17:17 PDT 2005 armv5b unknown Mar 05 22:24:23 kfm82slug:~/config root# uname -a Mar 05 22:24:25 Linux kfm82slug 2.4.22-xfs #1 Sun Jun 12 21:17:17 PDT 2005 armv5b unknown Mar 05 22:25:13 I'd really like to upgrade though because I need the FTP feature Mar 05 22:27:09 I don't know about what makes a pocket pc different that it would not work with the newer Samba release. Is this a known samba problem? Mar 05 22:28:32 Flipo_, what ftp feature are you talking about? Mar 05 22:29:43 ftp server, I know you can have it with unslung 5.5 but I'm not sure I want to mess around with packages and all Mar 05 22:30:54 unless you convince me it's really simple to do :P Mar 05 22:31:33 packages are the whole point of unslung (well one of the main points) Mar 05 22:32:22 but why ftp when setting up openssh and using scp is cleaner *and* more secure Mar 05 22:32:25 wow, he speaks ;) Mar 05 22:32:31 yeah, yeah Mar 05 22:32:49 been sick (actually still am with bronchitis/flu) Mar 05 22:33:29 Byron : I'd have to investigate I guess there are some tutorials for this on the wiki pages ? Mar 05 22:33:47 actually the last half year has been non-stop sick / suckiness with family here Mar 05 22:34:08 and I was so hoping that 2006 would be better than the last couple months of 2005 Mar 05 22:34:29 Flipo_, plenty of howtos in the wiki Mar 05 22:35:00 most of them very "step by minute step" variety and feel free to correct issues that you may or may not find Mar 05 22:35:02 so, 2006 is only 3 month old, i hope that the things will go better for your family and yourself Mar 05 22:35:25 caplink811_log, me too Mar 05 22:35:26 # ipkg install proftpd Mar 05 22:35:35 or ipkg install vsftpd Mar 05 22:35:49 is there a place with a more general description of SSH, I'm not familiar with it Mar 05 22:35:57 caplink811_log, unless you enjoy having chroots, in which case you really should go with pro Mar 05 22:36:24 Flipo_, have a look at www.openssh.org (imho) Mar 05 22:37:02 thanks Mar 05 22:38:01 caplink811_log, www.openbsd.org Mar 05 22:38:09 The thing to remember about ssh and unslung is that it looks much harder than it is. Just "ipkg install openssh", then on your pc, install PuTTY -- then use it the same way you use telnet. It's as easy as that to get it running. And PuTTY comes with an FTP-like interface that uses SSH's SCP feature to copy files. Easy. Mar 05 22:38:39 Flipo_, if you are in a windows environment, then http://www.chiark.greenend.org.uk/~sgtatham/putty/ and http://winscp.net/eng/index.php are usefull, too Mar 05 22:38:48 mwester : when using that method, is the slug still avalaible via samba ? Mar 05 22:39:00 Yes. Mar 05 22:39:04 I use winscp too Mar 05 22:39:29 And the SSH stuff works the same on Unslung 5.5 and the upcoming 6.x as well. Mar 05 22:40:07 kfm82, running debian and ubuntu here, so, openbsd is to specail for me ;) Mar 05 22:40:07 only problem is I will probably be stuck at 5.5 because of that Pocket PC bug :( Mar 05 22:41:02 ey, ByronT what's about a beta release of unslung-6.7 ? Mar 05 22:41:25 it's being worked on... right, mwester? Mar 05 22:41:29 ;) Mar 05 22:41:58 You're are working on 6.x Byron ? Mar 05 22:42:33 caplink811_log, Flipo_ i hope you're not installing beta / alpha quality system software onto slugs in a DMZ Mar 05 22:42:54 I'm still at R29 for now Mar 05 22:43:14 no, my "dmz" slug runs on 5.5 ;) Mar 05 22:43:15 Flipo_, actually mwester is doing the heavy lifting on 6.x right now Mar 05 22:43:56 kfm82, why you ask? any known problems with 6.x unslung on that topic? Mar 05 22:44:03 Ok, is there a place where I can submit bugs ? this is probably a linksys bug but I guess you guys might have some ways of fixing linksys code ? Mar 05 22:44:32 caplink811_log, ByronT, i am not sure yet if i can really trust the 5.5 version with unfiltered incoming traffic to be honest Mar 05 22:44:48 Flipo_, http://slugbug.nslu2-linux.org/ it is maybe Mar 05 22:45:04 * mwester back for second... Mar 05 22:45:34 but if the error is with just linksys firmware, it needs to be reported to linksys primarily Mar 05 22:45:43 hmm, what would the path to the openssl development libraries be from unslung-devel? Mar 05 22:46:09 I did report it, they said they would forward it to the firmware team but I'm always scared they just ignore the request Mar 05 22:46:21 for configur'ing things :p Mar 05 22:46:26 I wouldn't trust Unslung nor the Linksys firmware in a DMZ, but I did blast my 5.5-beta with Core Impact, and it seemed to pass as well as the Red Hat systems did. Mar 05 22:47:08 * mwester ducks out to shovel snow for a moment, BRB Mar 05 22:49:12 mwester, what exactly does Core Impact do, I haven't come into contact with it yet Mar 05 22:54:50 kfm82, http://www.coresecurity.com/products/coreimpact/index.php Mar 05 22:59:07 ByronT, thanks Mar 05 23:19:14 hi Mar 05 23:20:01 NSLU2-IRC, you need to change your nickname Mar 05 23:20:21 I know have no clue how to lol Mar 05 23:20:40 use /nick newnickname Mar 05 23:21:12 - Mar 05 23:21:43 - Mar 05 23:21:45 :) Mar 05 23:23:30 welcome back Mar 05 23:23:46 thanks Mar 05 23:24:11 I have a question Im a newbie Mar 05 23:24:20 ~ask Mar 05 23:24:21 If you have a question, just ask, maybe someone have an answer... sometimes. Mar 05 23:24:28 i got problems with ipkg Mar 05 23:24:44 the problem is nothing happens Mar 05 23:24:56 "no such file" Mar 05 23:25:01 when you do what? Mar 05 23:25:13 for example ipkg update Mar 05 23:25:35 most likely, you're not unslung yet Mar 05 23:25:43 you have done a /sbin/unsling? Mar 05 23:26:00 or, you've changed the environment and the path is borked... Mar 05 23:27:22 when I try /sbin/unsling it says: Mar 05 23:27:25 and you have verified, that your relay unsling with the mount or df command which should show you, that your rootfs is on /dev/sda1 (assuming that you use a hd on port 1) Mar 05 23:27:28 Usage: /sbin/unsling disk1|disk2 Mar 05 23:27:52 Ihave done the df Mar 05 23:29:43 well, as unsling mentioned, do an unsling to disk1 or disk2 (what means, your external media is pluged in port 1 or 2) Mar 05 23:30:18 ake /sbin/unsling disk1 (e.g.) Mar 05 23:30:27 s/ake/aka/ Mar 05 23:30:28 caplink811_log meant: aka /sbin/unsling disk1 (e.g.) Mar 05 23:31:12 ok I see i try it Mar 05 23:32:50 its working Mar 05 23:33:46 you have follow the readme step by step Mar 05 23:33:51 +nslu2-readme Mar 05 23:33:59 ~nslu2-readme Mar 05 23:34:10 it says: Mar 05 23:34:15 Linking /usr/bin/ipkg executable on target disk Mar 05 23:34:43 ~help Mar 05 23:35:14 yes I have read and folow the readme Mar 05 23:37:43 so, after unsling, you should boot without a disk, login, plug the disk in, wait, and test all functions, use the change the password procedure, and then boot with disk pluged in, login with your new password, and verify with the mount, or df command, that you're unslung Mar 05 23:38:25 ok i try it now thanks Mar 05 23:38:39 * caplink811_log heading to bed now.. good luck with your try Mar 05 23:39:01 ByronT, it is your customer now ;) **** ENDING LOGGING AT Mon Mar 06 10:59:56 2006