August 2006 - Xymon - Xymon mailman web

Patch not done yet? was RE: rrd-data.log
by brodie＠mcw.edu 03 Aug '06

03 Aug '06

Hi Henrik: Below are snippets from rrd that are still causing the "Duplicate Error" on my end, even after applying the patch. In the cases where there's netstat and ifstat data shown together, I had to include both because those chunks of data came out right at the time the duplicate error appeared. Too hard to time/see which of those 2 chunks of data cause the problem. In other cases, only ifstat data caused the problem. Where I have large chunks of whitespace- that separates "instances" of the duplicate error occurring. =========== @@data#348|1154533834.591188|192.168.224.202||wolf13.hmgc.mcw.edu|netsta t data wolf13,hmgc,mcw,edu.netstat linux Ip: 56731 total packets received 0 forwarded 0 incoming packets discarded 56067 incoming packets delivered 65344 requests sent out Icmp: 648 ICMP messages received 0 input ICMP message failed. ICMP input histogram: destination unreachable: 89 echo requests: 559 648 ICMP messages sent 0 ICMP messages failed ICMP output histogram: destination unreachable: 89 echo replies: 559 Tcp: 4630 active connections openings 1 passive connection openings 1 failed connection attempts 0 connection resets received 0 connections established 46150 segments received 54675 segments send out 85 segments retransmited 0 bad segments received. 1 resets sent Udp: 9933 packets received 0 packets to unknown port received. 0 packet receive errors 10021 packets sent TcpExt: ArpFilter: 0 4616 TCP sockets finished time wait in fast timer 908 delayed acks sent 557 packets directly queued to recvmsg prequeue. 507580 packets directly received from backlog 554 packets directly received from prequeue 19157 packets header predicted 426 packets header predicted and directly queued to user TCPPureAcks: 7526 TCPHPAcks: 9608 TCPRenoRecovery: 0 TCPSackRecovery: 0 TCPSACKReneging: 0 TCPFACKReorder: 0 TCPSACKReorder: 0 TCPRenoReorder: 0 TCPTSReorder: 0 TCPFullUndo: 0 TCPPartialUndo: 0 TCPDSACKUndo: 0 TCPLossUndo: 35 TCPLoss: 0 TCPLostRetransmit: 0 TCPRenoFailures: 0 TCPSackFailures: 0 TCPLossFailures: 0 TCPFastRetrans: 0 TCPForwardRetrans: 0 TCPSlowStartRetrans: 0 TCPTimeouts: 85 TCPRenoRecoveryFail: 0 TCPSackRecoveryFail: 0 TCPSchedulerFailed: 0 TCPRcvCollapsed: 0 TCPDSACKOldSent: 0 TCPDSACKOfoSent: 0 TCPDSACKRecv: 0 TCPDSACKOfoRecv: 0 TCPAbortOnSyn: 0 TCPAbortOnData: 0 TCPAbortOnClose: 0 TCPAbortOnMemory: 0 TCPAbortOnTimeout: 0 TCPAbortOnLinger: 0 TCPAbortFailed: 0 TCPMemoryPressures: 0 @@ @@data#349|1154533834.591337|192.168.224.202||wolf13.hmgc.mcw.edu|ifstat data wolf13,hmgc,mcw,edu.ifstat linux eth1 Link encap:Ethernet HWaddr 00:30:6E:F3:0B:46 inet addr:192.168.96.113 Bcast:192.168.96.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:72022 errors:0 dropped:0 overruns:0 frame:0 TX packets:71139 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:21476056 (20.4 Mb) TX bytes:17076949 (16.2 Mb) Interrupt:56 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:189 errors:0 dropped:0 overruns:0 frame:0 TX packets:189 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:16228 (15.8 Kb) TX bytes:16228 (15.8 Kb) @@ @@data#507|1154533965.074399|192.168.224.202||bc1s2.phys.mcw.edu|ifstat data bc1s2,phys,mcw,edu.ifstat linux eth1 Link encap:Ethernet HWaddr 00:0D:60:1E:0E:DD inet addr:192.168.224.111 Bcast:192.168.224.255 Mask:255.255.255.0 inet6 addr: fe80::20d:60ff:fe1e:edd/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:43166350 errors:0 dropped:0 overruns:0 frame:0 TX packets:6166704 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:14398847028 (13731.8 Mb) TX bytes:2587305933 (2467.4 Mb) Interrupt:45 Memory:c0010000-c0020000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:104 errors:0 dropped:0 overruns:0 frame:0 TX packets:104 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:9752 (9.5 Kb) TX bytes:9752 (9.5 Kb) @@ @@data#740|1154534133.480180|192.168.224.202||dunn.hmgc.mcw.edu|netstat data dunn,hmgc,mcw,edu.netstat linux Ip: 9154191 total packets received 0 forwarded 0 incoming packets discarded 8170997 incoming packets delivered 15226980 requests sent out Icmp: 8961 ICMP messages received 9 input ICMP message failed. ICMP input histogram: destination unreachable: 16 echo requests: 8945 13860 ICMP messages sent 0 ICMP messages failed ICMP output histogram: destination unreachable: 4915 echo replies: 8945 Tcp: 33598 active connections openings 15245 passive connection openings 4 failed connection attempts 106 connection resets received 10 connections established 7841472 segments received 15058779 segments send out 412 segments retransmited 0 bad segments received. 2935 resets sent Udp: 315663 packets received 4901 packets to unknown port received. 0 packet receive errors 154341 packets sent TcpExt: 7 resets received for embryonic SYN_RECV sockets ArpFilter: 0 37618 TCP sockets finished time wait in fast timer 2 packets rejects in established connections because of timestamp 12809 delayed acks sent 2 delayed acks further delayed because of locked socket Quick ack mode was activated 1930 times 144921 packets directly queued to recvmsg prequeue. 7524 packets directly received from backlog 40929271 packets directly received from prequeue 47328 packets header predicted 135097 packets header predicted and directly queued to user TCPPureAcks: 5602771 TCPHPAcks: 2027416 TCPRenoRecovery: 47 TCPSackRecovery: 19 TCPSACKReneging: 0 TCPFACKReorder: 0 TCPSACKReorder: 0 TCPRenoReorder: 0 TCPTSReorder: 0 TCPFullUndo: 0 TCPPartialUndo: 0 TCPDSACKUndo: 0 TCPLossUndo: 39 TCPLoss: 55 TCPLostRetransmit: 0 TCPRenoFailures: 2 TCPSackFailures: 1 TCPLossFailures: 1 TCPFastRetrans: 166 TCPForwardRetrans: 8 TCPSlowStartRetrans: 35 TCPTimeouts: 151 TCPRenoRecoveryFail: 9 TCPSackRecoveryFail: 1 TCPSchedulerFailed: 0 TCPRcvCollapsed: 0 TCPDSACKOldSent: 1 TCPDSACKOfoSent: 0 TCPDSACKRecv: 0 TCPDSACKOfoRecv: 0 TCPAbortOnSyn: 0 TCPAbortOnData: 948 TCPAbortOnClose: 14 TCPAbortOnMemory: 0 TCPAbortOnTimeout: 4 TCPAbortOnLinger: 0 TCPAbortFailed: 0 TCPMemoryPressures: 0 @@ @@data#741|1154534133.480925|192.168.224.202||dunn.hmgc.mcw.edu|ifstat data dunn,hmgc,mcw,edu.ifstat linux eth0 Link encap:Ethernet HWaddr 00:09:3D:13:DC:AB inet addr:192.168.224.105 Bcast:192.168.224.255 Mask:255.255.255.0 inet6 addr: fe80::209:3dff:fe13:dcab/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:39290006 errors:0 dropped:0 overruns:0 frame:0 TX packets:15275236 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2864046246 (2.6 GiB) TX bytes:21735816115 (20.2 GiB) Interrupt:185 eth0:0 Link encap:Ethernet HWaddr 00:09:3D:13:DC:AB inet addr:192.168.224.107 Bcast:192.168.224.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:185 eth0:1 Link encap:Ethernet HWaddr 00:09:3D:13:DC:AB inet addr:192.168.224.160 Bcast:192.168.224.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:185 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:36728 errors:0 dropped:0 overruns:0 frame:0 TX packets:36728 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:5951488 (5.6 MiB) TX bytes:5951488 (5.6 MiB) @@

5 6

Availability report
by rsmrcina＠wi.rr.com 03 Aug '06

03 Aug '06

What is the difference between the types of availability reports (critical, non-green, all)? When I run each report, they appear to generate the same data. Thanks. -- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com Catch the WAVV! http://www.wavv.org WAVV 2007 - Green Bay, WI - May 18-22, 2007

3 3

[hobbit] Hobbit newbie from BB: differences and what may Ilose from migrating?
by brodie＠mcw.edu 03 Aug '06

03 Aug '06

Basically, you lose NOTHING when you change a BB server to a Hobbit server. At first, it'll look very similar. Life will be good. The BB clients can run untouched. However- once you start setting up a few *Hobbit* clients, you'll quickly see what Hobbit DOES-- and what a typical BB client does NOT do. That's the moment when you'll race to wipe BB completely. Took me about a week. :-) -----Original Message----- From: Jordan Mendler [mailto:jmendler at ucla.edu] Sent: Tuesday, August 01, 2006 8:43 PM To: hobbit at hswn.dk Subject: RE: [hobbit] Hobbit newbie from BB: differences and what may Ilose from migrating? Cool. I guess I'll add a second display to bb-hosts and give hobbit a run. I'll just use Shmux to deploy bb-hosts to all the clients (figured I'd mention that great application while I'm at it :-) Once again, thanks for all the help everyone, hopefully my next message here will be as a convert. Jordan

7 13

[hobbit] client info
by massimo.morsiani＠gilbarco.com 03 Aug '06

03 Aug '06

Hi Etienne, do you plan to introduce that centralized mode in BBWin just like hobbit client? Do you plan to add a GUI interface to BBWin just like BigBrother official client? Thank you. Regards. Massimo Morsiani Information Technology Dep. ------ Gilbarco S.p.a. via de' Cattani, 220/G 50145 Firenze tel: +39-055-30941 fax: +39-055-318603 email: massimo.morsiani at gilbarco.com web: http://www.gilbarco.it PS. Your BBWin was the kick-off to switch from BigBrother to HobbitMon. Thanks again! -----Original Message----- From: Etienne Grignon [mailto:etienne.grignon at gmail.com] Sent: mercoledì 2 agosto 2006 14.35 To: hobbit at hswn.dk Subject: Re: [hobbit] client info Hello Kolbjørn , 2006/8/2, Kolbjørn Barmen <kolbjorn.barmen at uninett.no>: > Is it possible to add more information to the "info" page? > > One thing I miss on that page is "Client version:" (especially now as > I upgrade BBWin client). > This is not possible for the moment. BBWin does not include the centralized mode for the moment so the hobbit server doesn't know anything about the client version used on the Windows hosts. Regards, -- Etienne GRIGNON To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk This message (including any attachments) contains confidential and/or proprietary information intended only for the addressee. Any unauthorized disclosure, copying, distribution or reliance on the contents of this information is strictly prohibited and may constitute a violation of law. If you are not the intended recipient, please notify the sender immediately by responding to this e-mail, and delete the message from your system. If you have any questions about this e-mail please notify the sender immediately.

2 1

[hobbit] Host Notes
by jonescr＠cisco.com 03 Aug '06

03 Aug '06

Henrik, Forgive me, as I am not thinking clearly today (it is Monday afterall). You give a patch for bb-webpage.c, but I am unclear as to whether I am supposed to replace the orig bb-webpage with this new one, or rename patched version to "hostnotes", and craft a "hostnotes.sh" to go in the cgi directory that calls it? I understand that using the header and footer file will give the notes the standard hobbit look, which will be nice. Please tell me again in different terms how I should do this (or maybe I should just read it tommorrow when I'm thinking better haha). Thanks, -Charles On Thu, Jul 27, 2006 at 07:05:04PM -0700, Charles Jones wrote: > Do you plan on adding a cgi to enable live editing of "notes" > (www/notes/hostname) files? I saw in the manpage for bb-gen mention of a > script on dead-cat that gives that functionality, but I would like to > eventually see something that builds a "nice looking" notes page that > has the same background and font color etc as the rest of the Hobbit > pages. Currently if you just put something in a notes file you get a big > ugly white screen with the raw text. > > Maybe a header/footer for the notes page would solve that? Here's a simple solution for viewing the host notes, using mostly the tools you already have: * a notes_header and notes_footer file, mostly cloned from the existing bb_header and bb_footer files. These go in your ~hobbit/server/web/ directory. * a simple CGI using the bb_webpage utility. This goes in your ~hobbit/cgi-bin/ directory. Testing this revealed a bug in bb_webpage, so there's a patch for it as well. To use this, add "--docurl=$CGIBINURL/hostnotes.sh?HOST=%s" to BBGENOPTS in hobbitserver.c and restart Hobbit. The CGI shell-script currently looks only for files named .../notes/HOSTNAME - you can probably figure out how to change this if you want to look for HOSTNAME.html, HOSTNAME.txt or whatever you like. Regards, Henrik --- web/bb-webpage.c 2006/05/03 21:12:33 1.8 +++ web/bb-webpage.c 2006/07/28 07:12:09 @@ -12,7 +12,7 @@ /* */ /*----------------------------------------------------------------------------*/ -static char rcsid[] = "$Id: bb-webpage.c,v 1.8 2006/05/03 21:12:33 henrik Exp $"; +static char rcsid[] = "$Id: bb-webpage.c,v 1.9 2006/07/28 07:12:00 henrik Exp $"; #include <stdio.h> #include <string.h> @@ -63,8 +63,8 @@ headfoot(stdout, hffile, "", "header", bgcolor); do { - n = fread(inbuf, sizeof(inbuf), 1, stdin); - if (n > 0) fwrite(inbuf, n, 1, stdout); + n = fread(inbuf, 1, sizeof(inbuf), stdin); + if (n > 0) fwrite(inbuf, 1, n, stdout); } while (n == sizeof(inbuf)); headfoot(stdout, hffile, "", "footer", bgcolor); <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML> <HEAD> <META HTTP-EQUIV="REFRESH" CONTENT="60"> <META HTTP-EQUIV="EXPIRES" CONTENT="Sat, 01 Jan 2001 00:00:00 GMT"> <TITLE>&BBBACKGROUND : Hobbit - Host notes for &HOSTNAME</TITLE>  <link rel="stylesheet" type="text/css" href="&BBMENUSKIN/menu.css">  <link rel="shortcut icon" href="&BBSKIN/favicon-&BBBACKGROUND.ico"> </HEAD> <BODY BGCOLOR="&BBBACKGROUND" BACKGROUND="&BBSKIN/bkg-&BBBACKGROUND.gif" TEXT="#D8D8BF" LINK="#00FFAA" VLINK="#FFFF44"> <TABLE SUMMARY="Topline" WIDTH="100%"> <TR><TD HEIGHT=16> </TD></TR>  <TR> <TD VALIGN=MIDDLE ALIGN=LEFT WIDTH="30%"> <FONT FACE="Arial, Helvetica" SIZE="+1" COLOR="silver"><B>&HOBBITLOGO</B></FONT> </TD> <TD VALIGN=MIDDLE ALIGN=CENTER WIDTH="40%"> <CENTER><FONT FACE="Arial, Helvetica" SIZE="+1" COLOR="silver"><B>Host notes - &HOSTNAME</B></FONT></CENTER> </TD> <TD VALIGN=MIDDLE ALIGN=RIGHT WIDTH="30%"> <FONT FACE="Arial, Helvetica" SIZE="+1" COLOR="silver"><B>&BBDATE</B></FONT> </TD> </TR> <TR> <TD COLSPAN=3> <HR WIDTH="100%"> </TD> </TR> </TABLE> <BR> <CENTER> <FONT FACE="Arial, Helvetica" SIZE="+1" COLOR="silver"> </CENTER> </FONT> <BR><BR> <TABLE SUMMARY="Bottomline" WIDTH="100%"> <TR> <TD> <HR WIDTH="100%"> </TD> </TR> <TR> <TD ALIGN=RIGHT><FONT FACE="Arial, Helvetica" SIZE="-2" COLOR="silver"><B><A HREF="http://hobbitmon.sourceforge.net/" <http://hobbitmon.sourceforge.net/%22>; style="text-decoration: none">Hobbit Monitor &HOBBITDREL</A></B></FONT></TD> </TR> </TABLE>  <script type="text/javascript" language="JavaScript" src="&BBMENUSKIN/menu.js"></script>  <script type="text/javascript" language="JavaScript" src="&BBMENUSKIN/menu_items.js"></script>  <script type="text/javascript" language="JavaScript" src="&BBMENUSKIN/menu_tpl.js"></script> <script type="text/javascript" language="JavaScript"> new menu (MENU_ITEMS, MENU_POS); </script> </BODY> </HTML>

3 3

Disk monitoring via free blocks
by JamesHorwath＠glic.com 03 Aug '06

03 Aug '06

I have very large file systems I need to monitor, and the standard hobbit/bb client monitors won't allow monitoring by bytes left, which is what I need. The deadcat site has been down for the past 2 days, and I didn't see anything but wish requests for byte free monitoring. I need this for AIX, does anyone have the bb disk client for bytes free they can send me, or give any quick pointers on how to do this natively in hobbit. My hobbit server is 4.1.2p1. At this point it appears I will have to roll my own byte free monitor. I would appreciate any tips or code anyone could supply. Regards, Jim ----------------------------------------- This message, and any attachments to it, may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are notified that any use, dissemination, distribution, copying, or communication of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately by return e-mail and delete the message and any attachments. Thank you.

2 1

[hobbit] core in hobbitd_alert, clientupdate
by David.Gore＠verizonbusiness.com 03 Aug '06

03 Aug '06

Backtrace on the core, this is the latest snapshot. I do not have the patience to fully test clientupdate, so I will assume it is broken otherwise and that it may be fixed in the final version. Regardless this is for hobbitd_alert: [hobbit at hobbit server]$ gdb bin/hobbitd_alert tmp/core.29742 GNU gdb Red Hat Linux (6.3.0.0-1.122rh) Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux-gnu"...Using host libthread_db library "/lib/libthread_db.so.1". warning: exec file is newer than core file. Reading symbols from shared object read from target memory...done. Loaded system supplied DSO at 0x4f2000 Core was generated by `hobbitd_alert --checkpoint-file=/home/hobbit/server/tmp/alert.chk --checkpoint-'. Program terminated with signal 6, Aborted. warning: svr4_current_sos: Can't read pathname for load map: Input/output error Reading symbols from /lib/libpcre.so.0...done. Loaded symbols for /lib/libpcre.so.0 Reading symbols from /lib/libc.so.6...done. Loaded symbols for /lib/libc.so.6 Reading symbols from /lib/ld-linux.so.2...done. Loaded symbols for /lib/ld-linux.so.2 #0 0x004f2402 in __kernel_vsyscall () (gdb) bt #0 0x004f2402 in __kernel_vsyscall () #1 0x00538159 in raise () from /lib/libc.so.6 #2 0x005396e3 in abort () from /lib/libc.so.6 #3 0x0805a0f3 in sigsegv_handler (signum=11) at sig.c:57 #4 <signal handler called> #5 0x0054dc46 in vfprintf () from /lib/libc.so.6 #6 0x00553282 in fprintf () from /lib/libc.so.6 #7 0x08049dd7 in save_checkpoint (filename=0x9878098 "/home/hobbit/server/tmp/alert.chk") at hobbitd_alert.c:242 #8 0x0804a9ea in main (argc=Cannot access memory at address 0xffffffff ) at hobbitd_alert.c:502 (gdb) q The cores match up with these entries in page.log: 2006-07-23 14:50:45 Worker process died with exit code 134, terminating 2006-07-23 20:02:22 Worker process died with exit code 134, terminating 2006-07-24 11:51:27 Worker process died with exit code 134, terminating And these in hobbitlaunch.log 2006-07-23 14:50:45 Task bbpage terminated, status 1 2006-07-23 20:02:22 Task bbpage terminated, status 1 2006-07-24 11:51:27 Task bbpage terminated, status 1 Server is Fedora Core 5.

2 2

hobbitd_rrdtool core
by ezigler＠uta.edu 03 Aug '06

03 Aug '06

Greetings, I have migrated from bigbrother to hobbit-4.2-beta-20060605. I have followed the documentation and hobbitd_rrdtool is the only thing that is not working properly. It keeps generating core files. The output is attached to this message. Any help would be greatly appreciated. Thank you, Erich Zigler

2 2

[hobbit] Oratns
by Vernon.Everett＠dpi.wa.gov.au 03 Aug '06

03 Aug '06

Hi Henrik Yes, it is my experience that you only have one listener per server, and it can handle multiple databases. However, here, and in my previous company, they have 2 separate listener instances when running Oracle Financials. The database has a listener, and the applications also have a listener. Two separate instances on two separate ports. In the case of the one server, they have no less than 6 listener instances running, on 6 different ports. Configuring separate listener tests as below may be the only way to go at this point. Sadly, this may all be a waste of time. I am growing weary of fighting all the politics to get Hobbit in as a monitoring system, and am on the verge of giving up the fight. Regards Vernon -----Original Message----- From: Henrik Stoerner [mailto:henrik at hswn.dk] Sent: Wednesday, 2 August 2006 3:26 PM To: hobbit at hswn.dk Subject: Re: [hobbit] Oratns On Wed, Aug 02, 2006 at 09:36:28AM +0800, Everett, Vernon wrote: > How do I make it check for more than one Oracle listener? > For reasons unknown to me, we are running multiple listeners on > separate ports on a server. I'm surprised - I thought you could not have more than one tns listener per system. Oh well - I don't know one bit about Oracle DB; I've only worked with their J2EE application server. The problem with it is that even though you can put multiple "oratns" tests into the bb-hosts file, each of them will cause a separate status message. So what you'll see on the Hobbit display is the result of only one of the tests. My best suggestion is to copy the [oratns] section in bb-services so you have [oratns], [oratns1], [oratns2] and so up to the number of listeners you have on a single host. Then you can define them with their respective port numbers in the bb-hosts file, like 1.2.3.4 name.domain.com # oratns1:1545 oratns2:1546 Then there will be separate status columns for each of the listeners. Regards, Henrik To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

1 0

Hobbit monitor security bugfix release - 4.1.2p2
by henrik＠hswn.dk 02 Aug '06

02 Aug '06

Version 4.1.2p2 of Hobbit has just been uploaded to SourceForge, and is available at http://sourceforge.net/project/showfiles.php?group_id=128058&package_id=140… This release fixes a security bug reported by Jason Kruse earlier today: File access via the Hobbit "config" method failed to restrict access to the Hobbit configuration directory. It is therefore possible for anyone with access to the Hobbit network daemon on port 1984 to read any file on the Hobbit server which is readable by the user running the hobbitd daemon. This problem affects all versions of Hobbit 4.0 and 4.1. Users are encouraged to update their Hobbit installation, or restrict network access to Hobbit network daemon (e.g. by implementing firewall rules restricting access to TCP port 1984). This version also includes all non-security patches that have been published since the release of version 4.1.2p1 in November 2005. Regards, Henrik Storner

1 0