Re: Cannot upgrade circular udev dependency

[David Liontooth]

On 2/16/22 9:26 AM, Greg Wooledge wrote:

On Wed, Feb 16, 2022 at 08:24:57AM -0800, David Liontooth wrote:

Still, where in pool is udev?

unicorn:~$ apt-get --reinstall --print-uris install udev
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 1,464 kB of archives.
After this operation, 0 B of additional disk space will be used.
'http://ftp.us.debian.org/debian/pool/main/s/systemd/udev_247.3-6_amd64.deb' 
udev_247.3-6_amd64.deb 1463624 MD5Sum:2e6e11d7cfd3069201b3ea65853c5a61

Under s for systemd, apparently.  Or at least, that's where it is *now*.
Who knows where it was in your version.

Very nice. I didn't know how to query the repository for location; thanks!

Re: Cannot upgrade circular udev dependency

[David Liontooth]

On 2/16/22 9:03 AM, Andy Smith wrote:

On Wed, Feb 16, 2022 at 07:19:34AM -0800, David Liontooth wrote:

Hi -- I have a machine, Linux ancient 2.6.36.2 #1 SMP Sun Dec 26 06:19:57
PST 2010 x86_64 GNU/Linux.

[…]


Since release 198, udev requires support for the following features in
the running kernel:

- inotify(2)    (CONFIG_INOTIFY_USER)
- signalfd(2)   (CONFIG_SIGNALFD)
- accept4(2)
- open_by_handle_at(2)  (CONFIG_FHANDLE)
- timerfd_create(2) (CONFIG_TIMERFD)
- epoll_create(2)   (CONFIG_EPOLL)
dpkg: error processing archive
/var/cache/apt/archives/udev_232-25+deb9u13_amd64.deb (--unpack):
  subprocess new pre-installation script returned error exit status 1
update-rc.d: warning: start and stop actions are no longer supported;
falling back to defaults
update-rc.d: warning: start and stop actions are no longer supported;
falling back to defaults
Errors were encountered while processing:
  /var/cache/apt/archives/udev_232-25+deb9u13_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

[…]


There are clearly lots of barriers put in to keep people from making
mistakes, but it's also keeping me from upgrading. Is there a solution?

To have ended up trying to run Debian stretch software on a 2.6.32
kernel you have made some pretty extreme decisions far outside what
Debian supports.

You have got to get onto a more modern kernel so you can upgrade
udev. If you somehow force udev to get installed while still running
that 2.6.32 kernel you will be in a world of pain because it just
won't work and you very likely won't complete another boot.

You haven't elaborated as to why any of the newer kernels you have
installed won't boot.

Cheers,
Andy


Thanks, Andy. I didn't have physical access to the machine, so I didn't 
know why the kernels didn't boot. But I revered to jesse in sources.list 
and was able to install a new kernel, which is now booting fine. So in 
spite of my extreme decisions, Debian handled the upgrade well.


Dave

Re: Cannot upgrade circular udev dependency

[David Liontooth]

On 2/16/22 7:48 AM, Greg Wooledge wrote:

On Wed, Feb 16, 2022 at 07:19:34AM -0800, David Liontooth wrote:

Hi -- I have a machine, Linux ancient 2.6.36.2 #1 SMP Sun Dec 26 06:19:57
PST 2010 x86_64 GNU/Linux.

This is not a Debian kernel.  You either built it yourself, or you got
it from some foreign Linux distribution.
True -- I used to compile my own kernels, though in this case, there's 
no particular need to. I just want a vanilla system at this point.

I can install a new kernel, but it won't boot into any of the new kernels:

root@ancient:~# update-grub
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-4.9.0-16-amd64
Found initrd image: /boot/initrd.img-4.9.0-16-amd64
Found linux image: /boot/vmlinuz-3.16.0-6-amd64
Found initrd image: /boot/initrd.img-3.16.0-6-amd64
Found linux image: /boot/vmlinuz-2.6.36.2
Found linux image: /boot/vmlinuz-2.6.36.1

Why not?  What happens when you try to boot one of them?  Are they missing
whatever features you needed to build a custom kernel to support?
I've only tried remotely, so I don't see what's happening. If I force it 
and the udev is wrong, won't the kernel fail?

I also cannot upgrade udev:

root@ancient:~# apt --fix-broken install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
...
The following additional packages will be installed:
   udev
The following packages will be upgraded:
   udev
1 upgraded, 0 newly installed, 0 to remove and 476 not upgraded.
Need to get 0 B/1,112 kB of archives.
After this operation, 6,381 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Reading database ... 64907 files and directories currently installed.)
Preparing to unpack .../udev_232-25+deb9u13_amd64.deb ...
Since release 198, udev requires support for the following features in
the running kernel:

- inotify(2)    (CONFIG_INOTIFY_USER)
- signalfd(2)   (CONFIG_SIGNALFD)
- accept4(2)
- open_by_handle_at(2)  (CONFIG_FHANDLE)
- timerfd_create(2) (CONFIG_TIMERFD)
- epoll_create(2)   (CONFIG_EPOLL)

You could rebuild your custom kernel to include those features.  Assuming
they existed in 2.6.36.

But... that says deb9.  That's a *whole* lot newer than your running
system.  Did you honestly expect a Debian 9 package to work on your
Debian 6 (or whatever it is) system?
I'm trying to upgrade from jesse to stretch. Maybe I should downgrade to 
jesse again and see if I can install a debian kernel first -- I'll try 
that!

I'm not finding udev packages in pool. Where are they located in the
repository tree? Is there an intermediate udev package that would allow me
for instance to boot linux 3.16.0-6-amd64?

You're running a version that's so old that I wouldn't expect to find
its packages in the normal locations.  You'd be better off using
snapshot.debian.org and downloading the obsolete versions that you require
by hand.


OK, very helpful, I'd forgotten about snapshots, that's great.

Still, where in pool is udev?


Finally. I tried using another machine to download udev 215-17+deb8u7 -- it
lets me download libudev 215-17+deb8u7, but even just downloading the udev
package is blocked by the dependency check.

     apt-get install --download-only udev=215-17+deb8u7 <== fails
     apt-get install --nodeps --download-only udev=215-17+deb8u7
E: Command line option --nodeps is not understood in combination with the
other options

And this one says deb8.
I was just trying to find something that would install, so I went back 
to a jesse repository for this.

Use dpkg -i to install individual Debian package files in these old
versions.  "apt-get install ./filename" didn't exist back then.  The
old way was to use dpkg -i, which led you to an incomplete state,
and then use "apt-get -f install" with no package names to let apt-get
try to fix the incomplete state.

OK, cool, thanks!

Or... you could install a newer version of Debian from scratch.  It might
be simpler than trying to salvage this Frankendebian installation.  (You've
got mixed up versions all over the place.  I don't think this is fixable
in any sane way.)
You may be right, but the machine is old and I'm not entirely confident 
I can get it to boot from a USB stick.

I'm still curious why you needed a custom kernel, though.  You'll want to
solve that mystery.  If there's something *unique* about this machine,
which would prevent a clean installation of Debian 11, you'll need to
address it, whatever it may be.


I just used to compile my own kernels as a matter of course -- maybe 
from way back; I first installed potato. I don't think it means there's 
anything unusual about this Supermicro machine, I see nothing in my 
ancient notes that would suggest it needs anything special.


Cheers,
Dave

Cannot upgrade circular udev dependency

[David Liontooth]

Hi -- I have a machine, Linux ancient 2.6.36.2 #1 SMP Sun Dec 26 
06:19:57 PST 2010 x86_64 GNU/Linux.


I can install a new kernel, but it won't boot into any of the new kernels:

root@ancient:~# update-grub
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-4.9.0-16-amd64
Found initrd image: /boot/initrd.img-4.9.0-16-amd64
Found linux image: /boot/vmlinuz-3.16.0-6-amd64
Found initrd image: /boot/initrd.img-3.16.0-6-amd64
Found linux image: /boot/vmlinuz-2.6.36.2
Found linux image: /boot/vmlinuz-2.6.36.1


I also cannot upgrade udev:

root@ancient:~# apt --fix-broken install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
...
The following additional packages will be installed:
  udev
The following packages will be upgraded:
  udev
1 upgraded, 0 newly installed, 0 to remove and 476 not upgraded.
Need to get 0 B/1,112 kB of archives.
After this operation, 6,381 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Reading database ... 64907 files and directories currently installed.)
Preparing to unpack .../udev_232-25+deb9u13_amd64.deb ...
Since release 198, udev requires support for the following features in
the running kernel:

- inotify(2)    (CONFIG_INOTIFY_USER)
- signalfd(2)   (CONFIG_SIGNALFD)
- accept4(2)
- open_by_handle_at(2)  (CONFIG_FHANDLE)
- timerfd_create(2) (CONFIG_TIMERFD)
- epoll_create(2)   (CONFIG_EPOLL)
dpkg: error processing archive 
/var/cache/apt/archives/udev_232-25+deb9u13_amd64.deb (--unpack):

 subprocess new pre-installation script returned error exit status 1
update-rc.d: warning: start and stop actions are no longer supported; 
falling back to defaults
update-rc.d: warning: start and stop actions are no longer supported; 
falling back to defaults

Errors were encountered while processing:
 /var/cache/apt/archives/udev_232-25+deb9u13_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

I'm also unable to download or install anything else; it's all blocked 
by udev. I cannot for instance install any of these available versions:


root@ancient:~# just available udev
udev:
  Installed: 175-7.2
  Candidate: 232-25+deb9u13
  Version table:
 241-5~bpo9+1 100
    100 http://ftp.debian.org/debian stretch-backports/main amd64 
Packages

 232-25+deb9u13 500
    500 http://security.debian.org stretch/updates/main amd64 Packages
 232-25+deb9u12 500
    500 http://mirrors.kernel.org/debian stretch/main amd64 Packages
    500 http://debian.lcs.mit.edu/debian stretch/main amd64 Packages
 215-17+deb8u13 500
    500 http://security.debian.org jessie/updates/main amd64 Packages
 215-17+deb8u7 500
    500 http://mirrors.kernel.org/debian jessie/main amd64 Packages
 *** 175-7.2 100
    100 /var/lib/dpkg/status

I'm not finding udev packages in pool. Where are they located in the 
repository tree? Is there an intermediate udev package that would allow 
me for instance to boot linux 3.16.0-6-amd64?


At one point there was an option to use "touch /etc/udev/kernel-upgrade" 
to overcome this exact problem, but it's not working to get me out of

2.6.36.2 and udev 175-7.2.

Finally. I tried using another machine to download udev 215-17+deb8u7 -- 
it lets me download libudev 215-17+deb8u7, but even just downloading the 
udev package is blocked by the dependency check.


    apt-get install --download-only udev=215-17+deb8u7 <== fails
    apt-get install --nodeps --download-only udev=215-17+deb8u7
E: Command line option --nodeps is not understood in combination with 
the other options


There are clearly lots of barriers put in to keep people from making 
mistakes, but it's also keeping me from upgrading. Is there a solution?


Cheers,
Dave

Re: interfaces file failes to set gateway

[David Liontooth]

Thank you, Bob -- much appreciated, including the update on the 
conventions for the interfaces file!


Cheers,
Dave

On 01/10/2012 11:12 AM, Bob Proulx wrote:

David Liontooth wrote:

This is my /etc/network/interfaces:

# The primary network interface
auto eth0
iface eth0 inet static
 address 192.168.0.26
 netmask 255.255.255.0
 network 192.168.0.0
 broadcast 192.168.0.255
 gateway 192.168.0.178

First, it would be good to remove the network and broadcast lines.
They are redundant information.  It used to be that the
debian-installer would create those as examples.  But those examples
have been removed and the d-i no longer creates those.  Recently there
has been a push to clean these up so that they are no longer
distributing such examples.  Here is a reference:

   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630551

Second, it would be good to update to the modern event driven style
replacing "auto eth0" with "allow-hotplug eth0" instead.  Or keep
"auto" and also add "allow-hotplug eth0" too.  That is supported.  The
presence of "auto" allows '/etc/init.d/networking restart' to work.
The presence of "allow-hotplug" allows it to be started and stopped
based upon it being detected by the kernel is an the modern code path
for all new systems.  These days it is probably the much better tested
of the two since the older way is deprecated.  I expect you are seeing
the deprecation warnings.

allow-hotplug eth0
iface eth0 inet static
 address 192.168.0.26
 netmask 255.255.255.0
 gateway 192.168.0.178

The format and contents of the file are documented here:

   
http://www.debian.org/doc/manuals/debian-reference/ch05.en.html#_the_network_interface_with_the_static_ip

I don't think either of those two things will affect the problem you
are seeing.  But they would both be good changes to make to update to
the current standards before trying to debug further.


I cloned this entire operating system, which as you see is on a
private subnet, to another box that is on a public network, and got
exactly the same problem (with a different gateway). I have other
machines on the same networks with the same configuration that don't
have this problem. What could be preventing the default gateway from
being set on boot?

This information leads me to believe that it is probably not in the
interfaces file.  The file looks okay to me (other than my comments
above) and therefore the problem is probably elsewhere.  The most
likely suspects would be one of the files in the /etc/network/*.d/*
directory.

   ls /etc/network/*.d/

Look through those files and see if any of those might be causing this
problem.  They would have been cloned with the other machine and that
also leads me to think the problem might be there.

Have you looked at the /var/log/syslog file and/or dmesg output to see
if there are any messages related to network setup that might be
clues?

Good luck!
Bob



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4f0c652f.8000...@cogweb.net

interfaces file failes to set gateway

[David Liontooth]

I've run into an odd problem: on two of my squeeze servers, the 
/etc/network/interfaces file fails to set the default gateway on boot.


I can add the gateway manually by issuing "route add default gw 
192.168.0.178 eth0" -- it works fine.


This is my /etc/network/interfaces:

# The primary network interface
auto eth0
iface eth0 inet static
address 192.168.0.26
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.255
gateway 192.168.0.178

I cloned this entire operating system, which as you see is on a private 
subnet, to another box that is on a public network, and got exactly the 
same problem (with a different gateway). I have other machines on the 
same networks with the same configuration that don't have this problem. 
What could be preventing the default gateway from being set on boot?


Cheers,
David



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4f0bbd4a.1030...@cogweb.net

How to install Debian on a server with a LSISAS1068E controller

[David Liontooth]

Hi Allan,

Do you have the PCI ID for the controller this worked on? Did it need 
megaraid_sas or mptsas?


I have what seems to be the same controller, the LSI SAS 1068E, but it 
is PCI ID 1000:0059 rather than 1000:0058.


It would really be helpful to know if my device is the same as the one 
you managed to get working.


Cheers,
David

Re: How to install Debian on a server with a LSISAS1068E controller?

Allan Wind
Fri, 17 Jul 2009 10:00:13 -0700

On 2009-07-15T14:16:45, Allan Wind wrote:
> I am trying to get my friend Debian Lenny going on a SuperMicro
> SuperServer 6026T-3RF.  It uses a LSISAS1068E SAS controller.
>
> The manual claims "RAID5 in the Windows OS Environment, and RAID
> 0, RAID 1, RAID 10 for the Linux OS)" which might be correct if
> you define "Linux OS" as RedHat or SuSE.  Neither the stable nor
> testing netinst finds any drives.

The testing netinst image is needed for the NICs, and disabling
software RAID by removing the jumper JPS2.


/Allan
--
Allan Wind
Life Integrity, LLC



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: continuation character in cron jobs

[David Liontooth]

Rick Pasotto wrote:

> On Sun, Oct 21, 2007 at 12:03:30PM -0700, David Liontooth wrote:
>> 
>> I'd like to use the continuation character \ in a cron job, but I get an
>> error when I do.
>> 
>> I use "crontab -e" to edit the crontab and have this sort of thing:
>> 
>> 30 5 * * *  script varable variable \
>> variable-text
>> 
>> when I try to save, I get this:
>> 
>> crontab: installing new crontab
>> "/tmp/crontab.kZ7WHF/crontab":122: bad minute
>> errors in crontab file, can't install
>> 
>> Does anyone know if there's a way to get cron to accept a continuation
>> character?
> 
> man (5) crontab
> 
>The ``sixth'' field (the rest of the line) specifies the command to
>be run.  The entire command  portion  of  the line, up to a newline
>or % character, will be executed by /bin/sh or by the shell specified
>in the SHELL variable of the crontab file.  Percent-signs (%) in the
>command, unless escaped with backslash (\), will be  changed  into
>newline characters, and all data after the first % will be sent to
>the command as standard input. There is no way to split a single
>command line onto multiple lines, like the shell's trailing "\".
> 

Thanks! Really appreciate the info.

I searched the man pages for 'continuation' but missed this. Too bad!

Cheers,
Dave


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

continuation character in cron jobs

[David Liontooth]

I'd like to use the continuation character \ in a cron job, but I get an
error when I do.

I use "crontab -e" to edit the crontab and have this sort of thing:

30 5 * * *  script varable variable \
variable-text

when I try to save, I get this:

crontab: installing new crontab
"/tmp/crontab.kZ7WHF/crontab":122: bad minute
errors in crontab file, can't install

Does anyone know if there's a way to get cron to accept a continuation
character?

This is Debian Sid's (vixie) cron 3.0pl1-100.

Cheers,
David





-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: dumb questions about video editing and camcorders...

[David Liontooth]

Kevin Mark wrote:

> On Fri, Apr 13, 2007 at 11:02:48AM -0500, Ron Johnson wrote:
>> > In Etch itself some of these programs seem to have been made into
>> > packages. But there doesn't seem to be a Debian package that combines
>> > them all into one grand editing suite
>> 
>> That's not The Unix Way.
>> 
>> Kino (which makes it very easy to pull video from your FireWire
>> camcorder) and dvdauthor will get you started.
>> 
> One thing not mentioned is video capture. The whole process involved:
> take video
> connect video to computer via an interface (firewire, usb, etc)
> use tool to do editing
> use tool to do subtitling
> 
> the transfer from camcorder to computer file does not have to be done by
> you, maybe you know someone who can do it and put it on a dvd. Other
> wise, you need something like a firewire interface and a camcorder that
> is computer compatible.
> coriander maybe whats needed:
> Description: control IEEE1394 digital camera
>  Coriander is a GUI that lets you control all the features of an
>  IEEE-1394 Digital Camera complying with the DC Specifications v1.04 or
>  later (see http://www.1394ta.org).
> -k

You may want to use dvgrab to get the footage and cinelerra to edit -- check
out the skolelinux version.

Dave

-- 
news


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: gparted errors

[David Liontooth]

michael wrote:

> In order to resolve lack of space in / (for /opt where Intel compilers
> like to live) I wish to repartition my HD. I tried a LiveCD of gparted
> but it gives a Kernel Panic. (NB The CD is okay since I've used it in
> another machine before.) The 'problem' machine is a Pentium III (IIRC)
> 450MHz machine with 2 hard drives. I get to the 'options' menu, don't
> add anything extra, then hit 'OKAY'. The CD spins for a couple of
> seconds then nothing seems to happen for about a minute. Then I am back
> on the text/console screen with a Kernel Panic message. The top lines I
> can read say
> 
> Process Swapper
> Stack
> Call trace
> <...> cdrom_start_read_continuation+0x0/0xb0 ...
> ...
> ...
> ...
> EIP [<...>] ide_execute_command
> <0> Kernel panic - not syncing
> Fatel execption in interrupt
> 
> Any thoughts?
> 
> Thanks, Michael

Partitioning is a hassle and potentially risky -- have you considered just
moving your /opt to another partition and symlinking?

Dave


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Waveform display

[David Liontooth]

I'd like to display the waveform of files in X11 -- is there a utility for
doing this? I looked at extace, but it seems to only work with the esound
daemon. I'm looking for a command-line tool.

Dave


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: feh won't make a montage in a script

[David Liontooth]

David Liontooth wrote:

> 
> I'm using feh, an image viewing utility, to make a montage of thumbnails,
> with this command in a bash script:
> 
> feh -m -W 1024 $FIL.img/$THUMBS/*.jpg -O $FIL.jpg
> 
> The man page explains,
> 
>-O FILE
> 
> "Just save the created montage to FILE without displaying it (use in
> scripts)."
> 
> When I run the script, I get this:
> 
> feh ERROR: Can't open X display. It *is* running, yeah?
> 
> X is running, but so what? I'd like to run the script when it's not. If I
> run the script from the command line, it works.
> 
> This could just be a bug, cf.
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=373209
> 
> Dave

I meant to say, "When I run the script in a crontab", I get the error -- not
when I run it from a KDE console.

I added to the bug report in Debian and filed a bug upstream at
http://linuxbrit.co.uk/feh/ticket/29 

I also found a workaround -- montage from imagemagick works from cron too:

montage -tile 15 -geometry +1,+1 $FIL.img/$THUMBS/*.jpg $FIL.jpg

Cheers,
Dave


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

feh won't make a montage in a script

[David Liontooth]

I'm using feh, an image viewing utility, to make a montage of thumbnails,
with this command in a bash script:

feh -m -W 1024 $FIL.img/$THUMBS/*.jpg -O $FIL.jpg

The man page explains,

   -O FILE 

"Just save the created montage to FILE without displaying it (use in
scripts)."

When I run the script, I get this:

feh ERROR: Can't open X display. It *is* running, yeah?

X is running, but so what? I'd like to run the script when it's not. If I
run the script from the command line, it works.

This could just be a bug, cf.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=373209

Dave


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

How to configure SMART monitoring with munin for 3ware RAID

[David Liontooth]

Just for the record, here's a howto for monitoring the individual disks in a
3ware RAID using munin. The syntax for finding the drives on a 2.6 kernel
is not exactly intuitive.

1. Install smartmontools and edit /etc/smartd.conf, adding this sort of
thing:

# Monitor 4 ATA disks connected to a 3ware 8500 controller. Start short 
# self-tests every day at 2am and rolling long self-tests Sundays 
# starting at midnight.
# Get the drive numbers from http://localhost:888/ 
/dev/twe0 -d 3ware,0 -H -C 0 -U 0 -m [EMAIL PROTECTED] -o on -S on -s
(S/../.././02|L/../../7/00)
/dev/twe0 -d 3ware,1 -H -C 0 -U 0 -m [EMAIL PROTECTED] -o on -S on -s
(S/../.././02|L/../../7/01)
/dev/twe0 -d 3ware,2 -H -C 0 -U 0 -m [EMAIL PROTECTED] -o on -S on -s
(S/../.././02|L/../../7/02)
/dev/twe0 -d 3ware,3 -H -C 0 -U 0 -m [EMAIL PROTECTED] -o on -S on -s
(S/../.././02|L/../../7/03)

/etc/init.d/restart smartmontools
Check syslog for receipts

Install munin and munin-node and edit /etc/munin/plugin-conf.d/munin-node,
adding:

[hddtemp_smartctl]
user root
env.drives hda hdb twe0_0 twe0_1 twe0_2 twe0_3 
env.type_twe0_0 3ware,0
env.type_twe0_1 3ware,1
env.type_twe0_2 3ware,2
env.type_twe0_3 3ware,3

[smart_*]
user root
group disk

[smart_twe0-0]
env.smartargs -H -i -c -l error -l selftest -l selective -a -d 3ware,0

[smart_twe0-1]
env.smartargs -a -d 3ware,1

[smart_twe0-2]
env.smartargs -a -d 3ware,2

[smart_twe0-3]
env.smartargs -a -d 3ware,3


Create symlinks in /etc/munin/plugins

smart_twe0-0 -> /usr/share/munin/plugins/smart_
smart_twe0-1 -> /usr/share/munin/plugins/smart_
smart_twe0-2 -> /usr/share/munin/plugins/smart_
smart_twe0-3 -> /usr/share/munin/plugins/smart_


/etc/init.d/munin-node restart
Check /var/log/munin/*log to verify the plugins are working -- you'll get
errors if they're not.

Dave





-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Cronjobs get the wrong time stamp in mail record

[David Liontooth]

Wayne Topa wrote:

> David Liontooth([EMAIL PROTECTED]) is reported to have said:
>> 
>> I'm running a script as a cron job on four machines, and get an e-mail
>> every time the job is completed. On three machines, the time stamp is the
>> time of the completion of the job; on the last one, the time stamp is
>> five minutes earlier. I've checked the time on the machine; it's correct
>> (maintained with ntpdate). What could possibly be causing a mail to be
>> timestamped five minutes (consistently) before the cron job it reports is
>> over?
>> 
> It would help if you, at least mention, which version of cron, and
> what you are running (stable, etch, testing, or unstable).  Also the
> same info on the machines that are working.  This list can give you a
> lot of help but only if you help us, help you.
> 

Hi Wayne,

Thanks -- this is Debian sid with cron 3.0pl1-99 and exim4 4.63-11 with
exim4-base, exim4-config, and exim4-daemon-light. I'm just wondering in
principle what could cause the timestamp to drift -- isn't it created when
the job is done? 

The typical e-mail receipt looks like below -- note that at the bottom it
says the job completed at 19:59:56 yet the e-mail is dated 19:46:03. How is
this possible?

Dave

Date: Fri, 22 Dec 2006 19:46:03 -0800
From: Cron Daemon <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Cron <[EMAIL PROTECTED]> channel 60, 60min, "On the Record with 
Greta", 4

Using pisa's drive tv1 with 195GB free
Preparing to record 2006-12-22_1900_FOX-News_On_the_Record_with_Greta
Initiating recording by pisa of
2006-12-22_1900_FOX-News_On_the_Record_with_Greta from channel 60,
on capture card 4, at 19:00:02, duration 3594 seconds
MP3 audio selected.
Forcing audio preload to 0, max pts correction to 0.

1 duplicate frame(s)!

1 duplicate frame(s)!

1 duplicate frame(s)!

CBR audio: 16000 bytes/sec, 576 bytes/block

-rw-r--r-- 1 tna tna 421921446 2006-12-22
19:59 
/tv1/2006/2006-12/2006-12-22/2006-12-22_1900_FOX-News_On_the_Record_with_Greta.avi
-rw-r--r-- 1 tna tna 59703 2006-12-22
19:59 
/tv1/2006/2006-12/2006-12-22/2006-12-22_1900_FOX-News_On_the_Record_with_Greta.txt

Completed capture by pisa on Friday 22 December 2006 at 19:59:56
Video and audio   file size 403M
Closed captioning file size 60K







-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Cronjobs get the wrong time stamp in mail record

[David Liontooth]

I'm running a script as a cron job on four machines, and get an e-mail every
time the job is completed. On three machines, the time stamp is the time of
the completion of the job; on the last one, the time stamp is five minutes
earlier. I've checked the time on the machine; it's correct (maintained
with ntpdate). What could possibly be causing a mail to be timestamped five
minutes (consistently) before the cron job it reports is over?

Dave


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Daemonologists wanted

[David Liontooth]

Paul Johnson wrote:

> David Liontooth wrote:
> 
>> It might even be worth bugreporting the behavior that the sensor daemon
>> fails if a probed sensor is absent, but I suspect that's a Debian issue,
>> not an upstream sensors issue?
> 
> Yes, reportbug would be the appropriate method to report this bug.

See bug #372955 for a good example of how misleading the error message is to
a newbie. I posted a followup.

Dave


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Daemonologists wanted

[David Liontooth]

Paul Johnson wrote:

> For posterity, it might be helpful to post what motherboard and chipset
> that's for.

Right -- this is a Gigabyte K8NS Ultra-939. The Gigabyte K8NSC-939 has the
same "AMD Athlon64/FX or Opteron temperature sensor", as does the Tyan
Tomcat S8350 and lots of other amd64 boards -- basically anything with
the "00:18.3 Host bridge: Advanced Micro Devices [AMD] K8
[Athlon64/Opteron] Miscellaneous Control" chip, as shown by lspci. The
driver is new in 2.6.19 and works fine.

It might even be worth bugreporting the behavior that the sensor daemon
fails if a probed sensor is absent, but I suspect that's a Debian issue,
not an upstream sensors issue?

Dave



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Daemonologists wanted

[David Liontooth]

Paul Johnson wrote:

> David Liontooth wrote:
> 
>> 
>> If I issue
>> 
>> /etc/init.d/sensord start
>> 
>> to start the sensor daemon, the script seems to run fine, but the daemon
>> doesn't actually start. On my other machines, it runs as expected. Any
>> daemonologists out there?
> 
> What's the .conf look like?  Any log entries after you try starting
> sensord?

Hi Paul,

Thanks! I had this working on 2.8.18.3, and it failed after moving to a
kernel.org 2.6.19.1 kernel -- 

The receipt suggests the daemon starts:

# /etc/init.d/sensord start
Starting sensor daemon: sensord.

But you're right - the syslog shows the failure:

Dec 20 10:36:14 chianti sensord: sensord started
Dec 20 10:36:14 chianti sensord: Chip: k8temp-pci-00c3
Dec 20 10:36:14 chianti sensord: Adapter: PCI adapter
Dec 20 10:36:14 chianti sensord:   Mboard: 31.00
Dec 20 10:36:14 chianti sensord: Error getting sensor data: k8temp/temp2:
Can't access procfs/sysfs file
Dec 20 10:36:14 chianti sensord: sensord failed

It turns out the solution was to add a couple of ignores to the
configuration (previous conf below):

chip "k8temp-*"

   label temp1 "Mboard"
   ignore temp2
   label temp3 "CPU k8"
   ignore temp4

The error messages are not very helpful to newbies -- now I realize
that "Can't access procfs/sysfs file" means "there isn't any temp2 sensors
according to /proc or /sys, so I'm going to fail". A newbie like myself
might think sensors isn't seeing /proc or /sys, or that these file systems
aren't correctly installed, and so on. In any case, the default behavior
shouldn't be to fail because some ignore statements are missing!

Thanks for your help -- that's really all I needed, and hopefully this will
be useful for someone else.

Dave

 Here begins the real configuration file

chip "it87-*" "it8712-*"

# The values below have been tested on Gigabyte K8NSC-939 and K8NS Ultra-939

# Voltage monitors as advised in the It8705 data sheet
label in0 "VCore 1"
label in1 "VCore 2"
label in2 "+3.3V"
label in3 "+5V"
label in4 "+12V"
label in5 "-12V"
label in6 "-5V"
label in7 "Stdby"

# Conversions
compute in3 ((10/10)+1)*@ ,  @/((10/10)+1)
compute in4 ((30/10) +1)*@  , @/((30/10) +1)
compute in5 (7.67 * @) - 27.36  ,  (@ + 27.36) / 7.67
compute in6 (4.33 * @) - 13.64  ,  (@ + 13.64) / 4.33
compute in7 ((6.8/10)+1)*@ ,  @/((6.8/10)+1)

# Temperature
label temp1   "M/B Temp"
set   temp1_over  40
set   temp1_low   15
label temp2   "CPU Temp"
set   temp2_over  45
set   temp2_low   15
ignore temp3

# Fans
   set fan1_min 2500
# Fan2 is currently the power supply fan -- not sure how fast it should run
   set fan2_min 1000
   ignore fan3


chip "k8temp-*"

   label temp1 "Mboard"
   label temp3 "CPU k8"




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Daemonologists wanted

[David Liontooth]

If I issue

/etc/init.d/sensord start

to start the sensor daemon, the script seems to run fine, but the daemon
doesn't actually start. On my other machines, it runs as expected. Any
daemonologists out there?

Dave

#!/bin/sh -xv

PATH=/bin:/usr/bin:/sbin:/usr/sbin
+ PATH=/bin:/usr/bin:/sbin:/usr/sbin
DAEMON=/usr/sbin/sensord
+ DAEMON=/usr/sbin/sensord
# PIDFILE=/var/run/sensord.pid
CONFIG=/etc/default/sensord
+ CONFIG=/etc/default/sensord

test -x $DAEMON || exit 0
+ test -x /usr/sbin/sensord

if [ -f $CONFIG ]; then . $CONFIG; fi
+ '[' -f /etc/default/sensord ']'
+ . /etc/default/sensord
# Interval between scanning for alarms; e.g., 30s, 1m, 1h
ALARM_INTERVAL=30m
++ ALARM_INTERVAL=30m
# Interval between logging sensor measurements; e.g., 30s, 1m, 1h
LOG_INTERVAL=1h
++ LOG_INTERVAL=1h
# Syslog facility to use
SYSLOG_FACILITY=daemon
++ SYSLOG_FACILITY=daemon
# Libsensors config file to use
# CONFIG_FILE=/etc/sensors.conf
# Chips to scan
# SCAN_CHIPS=...

# Uncomment this to enable a 7-day round-robin database of sensor
# readings.  See the ROUND ROBIN DATABASES section of the sensord
# manual page for details.
# RRD_FILE=/var/log/sensord.rrd
# Interval between RRD readings; e.g. 30s, 5m (default), 1h
# RRD_INTERVAL=5m
# Include the load average in the RRD file.  If you enable this you
# must remove your old RRD file and rebuild your CGI script.
# RRD_LOADAVG=yes

if [ -n "$ALARM_INTERVAL" ]; then ALARM_INTERVAL="-i $ALARM_INTERVAL"; fi
+ '[' -n 30m ']'
+ ALARM_INTERVAL='-i 30m'
if [ -n "$LOG_INTERVAL" ]; then LOG_INTERVAL="-l $LOG_INTERVAL"; fi
+ '[' -n 1h ']'
+ LOG_INTERVAL='-l 1h'
if [ -n "$SYSLOG_FACILITY" ]; then SYSLOG_FACILITY="-f $SYSLOG_FACILITY"; fi
+ '[' -n daemon ']'
+ SYSLOG_FACILITY='-f daemon'
if [ -n "$CONFIG_FILE" ]; then CONFIG_FILE="-c $CONFIG_FILE"; fi
+ '[' -n '' ']'
if [ -n "$RRD_FILE" ]; then RRD_FILE="-r $RRD_FILE"; fi
+ '[' -n '' ']'
if [ -n "$RRD_INTERVAL" ]; then RRD_INTERVAL="-t $RRD_INTERVAL"; fi
+ '[' -n '' ']'
if [ -n "$RRD_LOADAVG" ]; then RRD_LOADAVG="-a"; fi
+ '[' -n '' ']'

case "$1" in
  start)
  echo -n "Starting sensor daemon:"
  echo -n " sensord"
if start-stop-daemon --quiet --stop --signal 0 --exec $DAEMON --name
sensord
  then
   echo " already running."
   exit
  fi
  /sbin/start-stop-daemon --start --quiet --exec $DAEMON -- $ALARM_INTERVAL
$LOG_INTERVAL $SYSLOG_FACILITY $RRD_INTERVAL $RRD_FILE $RRD_LOADAVG
$CONFIG_FILE $SCAN_CHIPS
  echo "."
  ;;
  stop)
  echo -n "Stopping sensor daemon: sensord"
  if start-stop-daemon --quiet --stop --signal 0 --exec $DAEMON --name
sensord
  then
   start-stop-daemon --quiet --stop --exec $DAEMON --name sensord
   # Now we wait for it to die
   # while kill -0 $PID 2>/dev/null; do sleep 1; done
   while start-stop-daemon --quiet --stop --signal 0 --exec $DAEMON --name
sensord 2>/dev/null; do sleep 1; done
   echo "."
  else
   echo " not running.";
  fi
  ;;
  force-reload|restart)
  $0 stop
  $0 start
  ;;
  *)
  echo "Usage: /etc/init.d/sensord {start|stop|restart|force-reload}"
  exit 1
esac
+ case "$1" in
+ echo -n 'Starting sensor daemon:'
Starting sensor daemon:+ echo -n ' sensord'
 sensord+ start-stop-daemon --quiet --stop --signal
0 --exec /usr/sbin/sensord --name sensord
+ /sbin/start-stop-daemon --start --quiet --exec /usr/sbin/sensord -- -i
30m -l 1h -f daemon
+ echo .
.

exit 0
+ exit 0
[EMAIL PROTECTED]:/etc#  


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]