Re: send req failed: Message too long
On Wed, 24 Sep 2003, Nicolas Ecarnot wrote: > Nicolas Ecarnot a écrit : > > Hi, > > > > I recently had this kind of problem with my amanda server. It has to > > backup around 120 samba clients : > > > > GETTING ESTIMATES... > > planner: time 0.371: dgram_send_addr: sendto(192.168.10.66.10080) > > failed: Message too long > > send req failed: Message too long > > I'm sorry to insist but this problem is really blocking me and I don't > really know what to do to solve it. > > I read in the faq that this may be due to an UDP packet size problem. > The suggested workaround is to shorten the names used in the directories > to save. > Unfortunately, I'm backing up many samba clients, and their names can't > be all changed, and I have no way to create symbolic links or that knid > of things. > > In my disklist, I have 120 lines like this : > backup.foo.com //winHost001/share nocomp-user-gnutar > > * I don't know HOW I could shorten this ? The other way to work around this problem is to employ multiple smbclient machines. So run some samba clients through backup.foo.com and some other samba clients through backup2.foo.com, etc. -Mitch
Re: send req failed: Message too long
Nicolas Ecarnot a écrit : Hi, I recently had this kind of problem with my amanda server. It has to backup around 120 samba clients : GETTING ESTIMATES... planner: time 0.371: dgram_send_addr: sendto(192.168.10.66.10080) failed: Message too long send req failed: Message too long I'm sorry to insist but this problem is really blocking me and I don't really know what to do to solve it. I read in the faq that this may be due to an UDP packet size problem. The suggested workaround is to shorten the names used in the directories to save. Unfortunately, I'm backing up many samba clients, and their names can't be all changed, and I have no way to create symbolic links or that knid of things. In my disklist, I have 120 lines like this : backup.foo.com //winHost001/share nocomp-user-gnutar * I don't know HOW I could shorten this ? In the faq, it's also written that the ability to use 64k udp packet size is OS-dependent. I'm running FreeBSD 5.1. * Perhaps there's a way to check its inetd abilities ? -- Nicolas Ecarnot
send req failed: Message too long
Hi, I recently had this kind of problem with my amanda server. It has to backup around 120 samba clients : GETTING ESTIMATES... planner: time 0.371: dgram_send_addr: sendto(192.168.10.66.10080) failed: Message too long send req failed: Message too long I read a bit of information on the yahoo archive, and found this problem had been worked around with the ctimeout variable. (I guess ? I'm not sure I understood everything). So I increased this timeout, and this morning, all my samba clients went fine. Cool. Now, as I'm still testing, I want to relaunch an amanda dump. I just launch exactly the same config, and this time, I get this bad old 'message too long'. Is there a standard solution ? I don't mind if my clients waste 5 minutes to answer, but I want to be sure my backups are done. Should I increase the ctimeout ? Or is there a way to ask the estimates in a sequential way, in order to avoid too long messages for inetd ? -- Nicolas Ecarnot
