Re: [Bacula-users] SD craches during backup with Network send error to SD
Hi Christoph Christoph Haas a écrit : On Saturday 15 October 2005 20:51, François Roels wrote: I'm not able to backup my server any longer. Le backup processes crach after any attempt without usefull (for me) message. I have filed a bug report against the package a week ago on the BTS (Debian's bug tracking system). See: http://bugs.debian.org/332743 Perhaps these two cases are related? (Question asked in direction of the honored Bacula development crew.) Kind regards Christoph Humm... doesn't seem to be a related problem. The medium is a disk and the local backups (the catalog) are working well. I'm trying to investigate using the Arno advice... François --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] SD craches during backup with Network send error to SD
On Sunday 16 October 2005 01:49, Dan Langille wrote: No temperature being raised here. I'm asking questions so as to understand the process better. I apologize if I got your intention wrong. Sounded like bashing for me. Yes, there could be. I would expect you to establish that there was a bug before logging a bug report. That sounded strange to my ears like you implied I should magically verify I really found a bug instead of having an administrative problem here. I couldn't imagine how I was to do that since I'm not a Bacula developer. Many bug reports I've seen sound like process foobar has disappeared - the last log line I found was yipyap instead of the pointer assignment in line 3917 of the devices.c is not checking the return value. In the case I reported the storage daemon just seems to disappear. I didn't attach an strace to it or look into the source code yet. That process sounds inefficient and places too much work upon the packager. I didn't not invent this procedure. It was established long before I started to be involved in Debian. But it works pretty well. And Debian users appreciate that they do not have to find out whether there is a problem in the upstream package, a problem in the way the Debian package was built, a side-effect with another package or just a misconfiguration. People can check whether other users encountered the same problem (that's the first thing they are asked when they tell of problems with a package). And often there are workarounds in the bug reports that help you get the software working before a fixed package can be provided publicly. Kind regards Christoph -- ~ ~ .signature [Modified] 1 line --100%--1,48 All --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] SD craches during backup with Network send error to SD
On 16 Oct 2005 at 12:30, Christoph Haas wrote: On Sunday 16 October 2005 01:49, Dan Langille wrote: Yes, there could be. I would expect you to establish that there was a bug before logging a bug report. That sounded strange to my ears like you implied I should magically verify I really found a bug instead of having an administrative problem here. I couldn't imagine how I was to do that since I'm not a Bacula developer. You could ask here. I would expect this list to be the first resource for anyone experiencing problems with Bacula. We'll quickly tell you whether or not it's a bug or a configuration issue. -- Dan Langille : http://www.langille.org/ BSDCan - The Technical BSD Conference - http://www.bsdcan.org/ --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] SD craches during backup with Network send error to SD
Hello, On 15.10.2005 20:51, François Roels wrote: Hi list I'm not able to backup my server any longer. Le backup processes crach after any attempt without usefull (for me) message. Any idea or processing advice ? Jupiter is a SBS Win2003 server on a LAN. Bacula is a Debian Sarge server with storage on a (FAT32 external) disk. Backup was originaly working during tests (backups were lunched from the Windows side). Now, the SD process craches silently every time the server's backup runs. (the local catalog backup runs without any trouble) No msg in syslog. All compinents are 1.36.2. The only trace is : 15-Oct 19:34 bacchus-dir: No prior Full backup Job record found. 15-Oct 19:34 bacchus-dir: No prior or suitable Full backup found. Doing FULL backup. 15-Oct 19:34 bacchus-dir: Start Backup JobId 75, Job=Jupiter.2005-10-15_19.34.56 *messages 15-Oct 19:35 bacchus-sd: Volume Jupiter-0001 previously written, moving to end of data. 15-Oct 20:36 jupiter-fd: Jupiter.2005-10-15_19.34.56 Fatal error: ..\filed\../../filed/backup.c:477 Network send error 27328 to SD. ERR=Une connexion existante a dû être fermée par l'hôte distant. The FD connects to the SD, and later that connection is closed. You might try the Heartbeat Interval settings, verify the firewall settings if there is one in between the client and the SD, and make sure that none of the computers you use goes into suspend mode. Arno 15-Oct 19:35 bacchus-dir: Jupiter.2005-10-15_19.34.56 Error: Bacula 1.36.2 (28Feb05): 15-Oct-2005 19:35:01 JobId: 75 Job:Jupiter.2005-10-15_19.34.56 Backup Level: Full (upgraded from Incremental) Client: jupiter-fd FileSet:Jupiter Documents Set 2005-09-18 01:05:02 Pool: PCpool Storage:File Start time: 15-Oct-2005 19:34:58 End time: 15-Oct-2005 19:35:01 FD Files Written: 4 SD Files Written: 0 FD Bytes Written: 72,768 SD Bytes Written: 0 Rate: 24.3 KB/s Software Compression: 27.3 % Volume name(s): Volume Session Id: 1 Volume Session Time:1129397677 Last Volume Bytes: 2,812,437,515 Non-fatal FD errors:0 SD Errors: 0 FD termination status: Error SD termination status: Error Termination:*** Backup Error *** Thanks for your advices. François --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users -- IT-Service Lehmann[EMAIL PROTECTED] Arno Lehmann http://www.its-lehmann.de --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] SD craches during backup with Network send error to SD
On Saturday 15 October 2005 20:51, François Roels wrote: I'm not able to backup my server any longer. Le backup processes crach after any attempt without usefull (for me) message. I have filed a bug report against the package a week ago on the BTS (Debian's bug tracking system). See: http://bugs.debian.org/332743 Perhaps these two cases are related? (Question asked in direction of the honored Bacula development crew.) Kind regards Christoph -- ~ ~ .signature [Modified] 1 line --100%--1,48 All --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] SD craches during backup with Network send error to SD
On 15 Oct 2005 at 21:04, Christoph Haas wrote: On Saturday 15 October 2005 20:51, François Roels wrote: I'm not able to backup my server any longer. Le backup processes crach after any attempt without usefull (for me) message. I have filed a bug report against the package a week ago on the BTS (Debian's bug tracking system). See: http://bugs.debian.org/332743 Perhaps these two cases are related? (Question asked in direction of the honored Bacula development crew.) Why did you log a Bacula bug in the Debian system? -- Dan Langille : http://www.langille.org/ BSDCan - The Technical BSD Conference - http://www.bsdcan.org/ --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] SD craches during backup with Network send error to SD
On Saturday 15 October 2005 22:56, Dan Langille wrote: On 15 Oct 2005 at 21:04, Christoph Haas wrote: On Saturday 15 October 2005 20:51, François Roels wrote: I'm not able to backup my server any longer. Le backup processes crach after any attempt without usefull (for me) message. I have filed a bug report against the package a week ago on the BTS (Debian's bug tracking system). See: http://bugs.debian.org/332743 Perhaps these two cases are related? (Question asked in direction of the honored Bacula development crew.) Why did you log a Bacula bug in the Debian system? Because there could be a bug in a Debian package. You probably rather wanted to ask: Why did you not log a Bacula bug in the Bacula bug tracking system instead? Because that's the default way to report problem with a binary Debian package. It's the lazy end-user's way to tell the package maintainer that there is a problem. In case the package being shipped with Debian Sarge has a serious bug - perhaps even a security-relevant one - then Debian needs to take action quickly. That could mean packaging a slightly newer version or adding upstream patches to the old version by the package maintainer. Usually asking the (upstream) software developers means getting the reply ah, that has been fixed in a later version - please upgrade. But Debian doesn't work that way. The package maintainer's duty is to look into the bug report, hopefully verify the bug and decide whether to forward that report upstream. But perhaps you want to clarify. Regards Christoph -- ~ ~ .signature [Modified] 1 line --100%--1,48 All --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] SD craches during backup with Network send error to SD
On 15 Oct 2005 at 23:07, Christoph Haas wrote: On Saturday 15 October 2005 22:56, Dan Langille wrote: On 15 Oct 2005 at 21:04, Christoph Haas wrote: On Saturday 15 October 2005 20:51, François Roels wrote: I'm not able to backup my server any longer. Le backup processes crach after any attempt without usefull (for me) message. I have filed a bug report against the package a week ago on the BTS (Debian's bug tracking system). See: http://bugs.debian.org/332743 Perhaps these two cases are related? (Question asked in direction of the honored Bacula development crew.) Why did you log a Bacula bug in the Debian system? Because there could be a bug in a Debian package. Yes, there could be. I would expect you to establish that there was a bug before logging a bug report. You probably rather wanted to ask: Why did you not log a Bacula bug in the Bacula bug tracking system instead? No, I didn't want to ask that. I was quite precise with my choice of words. Because that's the default way to report problem with a binary Debian package. It's the lazy end-user's way to tell the package maintainer that there is a problem. In case the package being shipped with Debian Sarge has a serious bug - perhaps even a security-relevant one - then Debian needs to take action quickly. That could mean packaging a slightly newer version or adding upstream patches to the old version by the package maintainer. Usually asking the (upstream) software developers means getting the reply ah, that has been fixed in a later version - please upgrade. But Debian doesn't work that way. The package maintainer's duty is to look into the bug report, hopefully verify the bug and decide whether to forward that report upstream. That process sounds inefficient and places too much work upon the packager. -- Dan Langille : http://www.langille.org/ BSDCan - The Technical BSD Conference - http://www.bsdcan.org/ --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] SD craches during backup with Network send error to SD
On Saturday 15 October 2005 23:13, Dan Langille wrote: On 15 Oct 2005 at 23:07, Christoph Haas wrote: On Saturday 15 October 2005 22:56, Dan Langille wrote: On 15 Oct 2005 at 21:04, Christoph Haas wrote: On Saturday 15 October 2005 20:51, François Roels wrote: I'm not able to backup my server any longer. Le backup processes crach after any attempt without usefull (for me) message. I have filed a bug report against the package a week ago on the BTS (Debian's bug tracking system). See: http://bugs.debian.org/332743 Perhaps these two cases are related? (Question asked in direction of the honored Bacula development crew.) Why did you log a Bacula bug in the Debian system? Because there could be a bug in a Debian package. Yes, there could be. I would expect you to establish that there was a bug before logging a bug report. If a process suddenly dies without something useful in the logs then it smells suspiciously like a bug. There are lesser reasons to file a bug report. You probably rather wanted to ask: Why did you not log a Bacula bug in the Bacula bug tracking system instead? No, I didn't want to ask that. I was quite precise with my choice of words. If you were familiar with Debian then you would know the answer already. Otherwise your original question makes no sense to me. Because that's the default way to report problem with a binary Debian package. It's the lazy end-user's way to tell the package maintainer that there is a problem. In case the package being shipped with Debian Sarge has a serious bug - perhaps even a security-relevant one - then Debian needs to take action quickly. That could mean packaging a slightly newer version or adding upstream patches to the old version by the package maintainer. Usually asking the (upstream) software developers means getting the reply ah, that has been fixed in a later version - please upgrade. But Debian doesn't work that way. The package maintainer's duty is to look into the bug report, hopefully verify the bug and decide whether to forward that report upstream. That process sounds inefficient and places too much work upon the packager. Question it all you want. That's the way it works. Now if we can please get on-topic again. No need to raise the temperature with off-topic discussions. Christoph -- ~ ~ .signature [Modified] 1 line --100%--1,48 All --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] SD craches during backup with Network send error to SD
On 15 Oct 2005 at 23:38, Christoph Haas wrote: On Saturday 15 October 2005 23:13, Dan Langille wrote: On 15 Oct 2005 at 23:07, Christoph Haas wrote: On Saturday 15 October 2005 22:56, Dan Langille wrote: On 15 Oct 2005 at 21:04, Christoph Haas wrote: On Saturday 15 October 2005 20:51, François Roels wrote: I'm not able to backup my server any longer. Le backup processes crach after any attempt without usefull (for me) message. I have filed a bug report against the package a week ago on the BTS (Debian's bug tracking system). See: http://bugs.debian.org/332743 Perhaps these two cases are related? (Question asked in direction of the honored Bacula development crew.) Why did you log a Bacula bug in the Debian system? Because there could be a bug in a Debian package. Yes, there could be. I would expect you to establish that there was a bug before logging a bug report. If a process suddenly dies without something useful in the logs then it smells suspiciously like a bug. There are lesser reasons to file a bug report. You probably rather wanted to ask: Why did you not log a Bacula bug in the Bacula bug tracking system instead? No, I didn't want to ask that. I was quite precise with my choice of words. If you were familiar with Debian then you would know the answer already. Otherwise your original question makes no sense to me. I know less about Debian than I thought. Because that's the default way to report problem with a binary Debian package. It's the lazy end-user's way to tell the package maintainer that there is a problem. In case the package being shipped with Debian Sarge has a serious bug - perhaps even a security-relevant one - then Debian needs to take action quickly. That could mean packaging a slightly newer version or adding upstream patches to the old version by the package maintainer. Usually asking the (upstream) software developers means getting the reply ah, that has been fixed in a later version - please upgrade. But Debian doesn't work that way. The package maintainer's duty is to look into the bug report, hopefully verify the bug and decide whether to forward that report upstream. That process sounds inefficient and places too much work upon the packager. Question it all you want. That's the way it works. I didn't question it at all. I provided my opinion. Now if we can please get on-topic again. Don't be so dimissive. Bug resolution is very much on-topic. Knowledge gathering helps that. No need to raise the temperature with off-topic discussions. No temperature being raised here. I'm asking questions so as to understand the process better. But as you wish. I'll bother you no more on this. -- Dan Langille : http://www.langille.org/ BSDCan - The Technical BSD Conference - http://www.bsdcan.org/ --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
