[plug] Eek.. help!

Daniel Pearson daniel at flashware.net
Fri Jul 7 14:48:15 WST 2006


Strange.. cause I haven't actually changed anything!

The box is running Samba (as it's my fileserver), and I thing I can't 
seem to get rid of from daemon.log is:
Jul  7 14:32:30 fs01 smbd[4029]: [2006/07/07 14:32:30, 0] 
lib/util_sock.c:get_peer_addr(1225)
Jul  7 14:32:30 fs01 smbd[4029]:   getpeername failed. Error was 
Transport endpoint is not connected
Jul  7 14:32:30 fs01 smbd[4029]: [2006/07/07 14:32:30, 0] 
lib/util_sock.c:get_peer_addr(1225)
Jul  7 14:32:30 fs01 smbd[4029]:   getpeername failed. Error was 
Transport endpoint is not connected
Jul  7 14:32:30 fs01 smbd[4029]: [2006/07/07 14:32:30, 0] 
lib/access.c:check_access(328)
Jul  7 14:32:30 fs01 smbd[4029]: [2006/07/07 14:32:30, 0] 
lib/util_sock.c:get_peer_addr(1225)
Jul  7 14:32:30 fs01 smbd[4029]:   getpeername failed. Error was 
Transport endpoint is not connected
Jul  7 14:32:30 fs01 smbd[4029]:   Denied connection from  (0.0.0.0)
Jul  7 14:32:30 fs01 smbd[4029]: [2006/07/07 14:32:30, 0] 
lib/util_sock.c:get_peer_addr(1225)
Jul  7 14:32:30 fs01 smbd[4029]:   getpeername failed. Error was 
Transport endpoint is not connected
Jul  7 14:32:30 fs01 smbd[4029]:   Connection denied from 0.0.0.0
Jul  7 14:32:30 fs01 smbd[4029]: [2006/07/07 14:32:30, 0] 
lib/util_sock.c:write_data(557)
Jul  7 14:32:30 fs01 smbd[4029]:   write_data: write failure in writing 
to client 10.1.1.13. Error Connection reset by peer
Jul  7 14:32:30 fs01 smbd[4029]: [2006/07/07 14:32:30, 0] 
lib/util_sock.c:send_smb(765)
Jul  7 14:32:30 fs01 smbd[4029]:   Error writing 5 bytes to client. -1. 
(Connection reset by peer)
Jul  7 14:36:11 fs01 smbd[3937]: [2006/07/07 14:36:11, 0] 
printing/pcap.c:pcap_cache_reload(159)
Jul  7 14:36:11 fs01 smbd[3937]:   Unable to open printcap file 
/etc/printcap for read!
Jul  7 14:36:11 fs01 smbd[3937]: [2006/07/07 14:36:11, 0] 
printing/pcap.c:pcap_cache_reload(159)
Jul  7 14:36:11 fs01 smbd[3937]:   Unable to open printcap file 
/etc/printcap for read!
Jul  7 14:41:07 fs01 smbd[4049]: [2006/07/07 14:41:07, 0] 
lib/util_sock.c:read_data(529)
Jul  7 14:41:07 fs01 smbd[4049]:   read_data: read failure for 4 bytes 
to client 10.1.1.11. Error = Connection reset by peer
Jul  7 14:42:25 fs01 smbd[3981]: [2006/07/07 14:42:25, 0] 
printing/pcap.c:pcap_cache_reload(159)
Jul  7 14:42:25 fs01 smbd[3981]:   Unable to open printcap file 
/etc/printcap for read!
Jul  7 14:42:25 fs01 smbd[3981]: [2006/07/07 14:42:25, 0] 
printing/pcap.c:pcap_cache_reload(159)
Jul  7 14:42:25 fs01 smbd[3981]:   Unable to open printcap file 
/etc/printcap for read!

I've specified in the smb.conf to not use printing, but it still doesn't 
seem to get rid of that message. Any ideas?

Cheers
*Daniel Pearson
*Flashware Solutions ABN 58 438 456 919
Mob: 0438 118 897  |  Email: daniel at flashware.net 
<mailto:daniel at flashware.net>

The information contained in this electronic transmission is 
confidential. If you are not the intended recipient of this 
transmission, use of this information is strictly prohibited.  If you 
have received this transmission in error, please contact Flashware 
Solutions 0438 118 897.


Tomasz Grzegurzko wrote:
> On 7/7/06, Daniel Pearson <daniel at flashware.net> wrote:
>>
>>  Ah, great - thanks. Been stressed out about the server just dieing, 
>> didn't
>> even take notice of the timestamp!
>>
>>
>>
>>  Daniel Pearson
>>  Flashware Solutions ABN 58 438 456 919
>>  Mob: 0438 118 897  |  Email: daniel at flashware.net
>>
>>  The information contained in this electronic transmission is 
>> confidential.
>> If you are not the intended recipient of this transmission, use of this
>> information is strictly prohibited.  If you have received this 
>> transmission
>> in error, please contact Flashware Solutions 0438 118 897.
>>
>>  Tomasz Grzegurzko wrote:
>> On 7/7/06, Tomasz Grzegurzko <tomasz89 at gmail.com> wrote:
>>
>> On 7/7/06, Daniel Pearson (Flashware Solutions) <daniel at flashware.net>
>> wrote:
>>  >
>>  >  I just had my server die, it was saying I/O error.
>>  >
>>  >  Have rebooted, and having a look in /var/log/messages I notice a 
>> lot of
>> the
>>  > following:
>>  >  Jul  3 01:27:25 fs01 -- MARK --
>>  >  Jul  3 01:47:26 fs01 -- MARK --
>>  >  Jul  3 02:07:26 fs01 -- MARK --
>>  >  Jul  3 02:27:26 fs01 -- MARK --
>>  >  Jul  3 02:47:27 fs01 -- MARK --
>>  >  Jul  3 03:07:27 fs01 -- MARK --
>>  >  Jul  3 03:27:28 fs01 -- MARK --
>>  >  Jul  3 03:47:28 fs01 -- MARK --
>>  >  Jul  3 04:07:28 fs01 -- MARK --
>>  >  Jul  3 04:27:29 fs01 -- MARK --
>>  >  Jul  3 04:47:29 fs01 -- MARK --
>>  >  Jul  3 05:07:30 fs01 -- MARK --
>>  >
>>  >  I have googled, but have not been able to find out what they mean 
>> - any
>>  > ideas?
>>  >
>>  >  Cheers
>>  >
>>  > --
>>  >
>>  >  Daniel Pearson
>>  >  Flashware Solutions ABN 58 438 456 919
>>  >  Mob: 0438 118 897  |  Email: daniel at flashware.net
>>  >
>>  >  The information contained in this electronic transmission is
>> confidential.
>>  > If you are not the intended recipient of this transmission, use of 
>> this
>>  > information is strictly prohibited.  If you have received this
>> transmission
>>  > in error, please contact Flashware Solutions 0438 118 897.
>>  > _______________________________________________
>>  > PLUG discussion list: plug at plug.org.au
>>  > http://www.plug.org.au/mailman/listinfo/plug
>>  > Committee e-mail: committee at plug.linux.org.au
>>  >
>>  >
>>  >
>>  They're normal. Every 30 minutes in your case, your syslog is making
>>  this entry.. You can think of it as a heartbeat or an "I'm alive!"
>>  message from your system...
>>
>>  Tomasz
>>
>>  Sorry 20 minutes! Wrong key..
>>  _______________________________________________
>>
>>  PLUG discussion list: plug at plug.org.au
>>  http://www.plug.org.au/mailman/listinfo/plug
>>  Committee e-mail: committee at plug.linux.org.au
>>
>>
>>
>> _______________________________________________
>> PLUG discussion list: plug at plug.org.au
>> http://www.plug.org.au/mailman/listinfo/plug
>> Committee e-mail: committee at plug.linux.org.au
>>
>>
>>
> No DMA errors are a good thing -- either DMA has been disabled and
> you're running in PIO mode smoothly, or it is enabled and you're
> running smoothly with DMA on now.
>
> Tomasz
> _______________________________________________
> PLUG discussion list: plug at plug.org.au
> http://www.plug.org.au/mailman/listinfo/plug
> Committee e-mail: committee at plug.linux.org.au
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.plug.org.au/pipermail/plug/attachments/20060707/ac5f00b2/attachment.html>


More information about the plug mailing list