|
From: Bradley J. <big...@gm...> - 2005-10-28 14:08:10
|
Jamie - This did fix the problem! Thanks alot. Unfortunately due to the nature of m= y hosting service, I can't set up a ping monitor as ping is restricted. Thanks! B On 27 Oct 2005 09:28:07 +1000, Jamie Cameron <jca...@we...> wrote: > > Hi Bradley, > > I had a look at the code, and I can see how this could happen.. If the > monitor gets notified that it will receive a packet but doesn't actually,= it > will fail as you described. > > The work-around is to edit the file status/ping-monitor.pl and insert the > following at line 114: > > next if (!$from_saddr); > > Let me know if that works.. > > - Jamie > > On Thu, 2005-10-27 at 01:46, Bradley Jonas wrote: > > *Hi all... > > I set up a ping monitor through the Server/System Status pages and due to > some glitches, the ping-monitor perl script is bombing with: > > Error - Perl execution failed > > Bad arg length for Socket::unpack_sockaddr_in, length is 0, should be 16 = at ping-monitor.pl line 114. > > > Anyway - I'm not sure how to fix it considering that the IP that I provid= ed is def. not 0 length. > I figured I'd try to remove the monitor, but I can't find any record of i= t in the /status/services directory. > > I've grepped through all of the files in the webmin directory and I can't= find any reference to it. > > Any ideas on how to fix or remove this monitor? > > Thanks > B > > > -- > "Look at him.....he runs like a Welshman........doesn't he run like a > Welshman?" > -Stewart Gilligan Griffin * > > -- "Look at him.....he runs like a Welshman........doesn't he run like a Welshman?" -Stewart Gilligan Griffin |