Unravel amstatus output
I set up Amanda on Friday to do an almost real backup job. I thought this would be the final test before putting it into operation. When I arrived at work this morning, I was somewhat surprised to see that the Amanda run doesn't seem to have finished. amstatus daily gives me some information, but I'm not sure how to interpret it. There are still 3 files on the holding disk, adding up to about 48GB. The tape drive doesn't seem to be doing anything - just sitting there quietly at the moment with no sign of activity. I won't include the entire output of amstatus daily, but here are extracts, if someone can please tell me if they see something wrong. I have many entries like these - seems to be one for each DLE: cerberus:/home 0 1003801k finished (22:18:15) Then these entries, which I think are the 2 that failed, as shown later in the summary: cerberus:/.autofsck 0 planner: [disk /.autofsck offline on cerberus?] cerberus:/.fonts.cache-1 0 planner: [disk /.fonts.cache-1 offline on cerberus?] Then these 3 that are the ones still on the holding disk: minerva:/home0 8774296k writing to tape (23:09:07) minerva:/usr/local/clients 0 32253287k dump done (1:08:27), wait for writing to tape minerva:/usr/local/development 0 9687648k dump done (23:48:17), wait for writing to tape And then this summary, which I'm not sure how to interpret: SUMMARY part real estimated size size partition : 109 estimated : 107 69631760k flush : 0 0k failed : 20k ( 0.00%) wait for dumping: 00k ( 0.00%) dumping to tape : 00k ( 0.00%) dumping : 0 0k 0k ( 0.00%) ( 0.00%) dumped : 107 58148656k 69631760k ( 83.51%) ( 83.51%) wait for writing: 2 41940935k 48107940k ( 87.18%) ( 60.23%) wait to flush : 0 0k 0k (100.00%) ( 0.00%) writing to tape : 1 8774296k 12515695k ( 70.11%) ( 12.60%) failed to tape : 0 0k 0k ( 0.00%) ( 0.00%) taped : 104 7433425k 9008125k ( 82.52%) ( 10.68%) 4 dumpers idle : not-idle taper writing, tapeq: 2 network free kps: 2000 holding space : 50295358k ( 49.79%) dumper0 busy : 2:53:47 ( 5.67%) dumper1 busy : 0:13:48 ( 0.45%) dumper2 busy : 0:00:00 ( 0.00%) taper busy : 0:12:38 ( 0.41%) 0 dumpers busy : 2+0:07:56 ( 94.22%)not-idle: 2+0:00:04 ( 99.73%) start-wait: 0:07:51 ( 0.27%) 1 dumper busy : 2:46:29 ( 5.43%)not-idle: 1:20:10 ( 48.15%) client-constrained: 1:18:08 ( 46.93%) no-bandwidth: 0:04:16 ( 2.57%) start-wait: 0:03:54 ( 2.35%) 2 dumpers busy : 0:10:34 ( 0.35%) client-constrained: 0:06:22 ( 60.27%) start-wait: 0:04:05 ( 38.76%) no-bandwidth: 0:00:06 ( 0.96%) 3 dumpers busy : 0:00:00 ( 0.00%) I would highly appreciate your insight into what is going on, especially for the 3 DLEs that are waiting for writing to tape. -- View this message in context: http://www.nabble.com/Unravel-amstatus-output-tf1953587.html#a5357597 Sent from the Amanda - Users forum at Nabble.com.
RE Unravel amstatus output
Looking with my newbie's eyes it seems that Amanda is running well. Just very slowly. And Amanda's log seems to indicate that the problem is on the tape drive side. The only thing strange that I see is the following line which say that your drive is busy only 0,41% of the time: taper busy : 0:12:38 ( 0.41%) What does it do the rest of the time??? [EMAIL PROTECTED] a écrit sur 17/07/2006 10:54:55 : I set up Amanda on Friday to do an almost real backup job. I thought this would be the final test before putting it into operation. When I arrived at work this morning, I was somewhat surprised to see that the Amanda run doesn't seem to have finished. amstatus daily gives me some information, but I'm not sure how to interpret it. There are still 3 files on the holding disk, adding up to about 48GB. The tape drive doesn't seem to be doing anything - just sitting there quietly at the moment with no sign of activity. I won't include the entire output of amstatus daily, but here are extracts, if someone can please tell me if they see something wrong. I have many entries like these - seems to be one for each DLE: cerberus:/home 0 1003801k finished (22:18:15) Then these entries, which I think are the 2 that failed, as shown later in the summary: cerberus:/.autofsck 0 planner: [disk /.autofsck offline on cerberus?] cerberus:/.fonts.cache-1 0 planner: [disk /.fonts.cache-1 offline on cerberus?] Then these 3 that are the ones still on the holding disk: minerva:/home 0 8774296k writing to tape (23:09:07) minerva:/usr/local/clients 0 32253287k dump done (1:08:27), wait for writing to tape minerva:/usr/local/development 0 9687648k dump done (23:48:17), wait for writing to tape And then this summary, which I'm not sure how to interpret: SUMMARY part real estimated sizesize partition: 109 estimated: 107 69631760k flush : 0 0k failed : 2 0k ( 0.00%) wait for dumping: 0 0k ( 0.00%) dumping to tape : 0 0k ( 0.00%) dumping : 0 0k 0k ( 0.00%) ( 0.00%) dumped : 107 58148656k 69631760k ( 83.51%) ( 83.51%) wait for writing: 2 41940935k 48107940k ( 87.18%) ( 60.23%) wait to flush : 0 0k 0k (100.00%) ( 0.00%) writing to tape : 1 8774296k 12515695k ( 70.11%) ( 12.60%) failed to tape : 0 0k 0k ( 0.00%) ( 0.00%) taped : 104 7433425k 9008125k ( 82.52%) ( 10.68%) 4 dumpers idle : not-idle taper writing, tapeq: 2 network free kps: 2000 holding space : 50295358k ( 49.79%) dumper0 busy : 2:53:47 ( 5.67%) dumper1 busy : 0:13:48 ( 0.45%) dumper2 busy : 0:00:00 ( 0.00%) taper busy : 0:12:38 ( 0.41%) 0 dumpers busy : 2+0:07:56 ( 94.22%) not-idle: 2+0:00:04 ( 99.73%) start-wait: 0:07:51 ( 0.27%) 1 dumper busy : 2:46:29 ( 5.43%) not-idle: 1:20:10 ( 48.15%) client-constrained: 1:18:08 ( 46.93%) no-bandwidth: 0:04:16 ( 2.57%) start-wait: 0:03:54 ( 2.35%) 2 dumpers busy : 0:10:34 ( 0.35%) client-constrained: 0:06:22 ( 60.27%) start-wait: 0:04:05 ( 38.76%) no-bandwidth: 0:00:06 ( 0.96%) 3 dumpers busy : 0:00:00 ( 0.00%) I would highly appreciate your insight into what is going on, especially for the 3 DLEs that are waiting for writing to tape. -- View this message in context: http://www.nabble.com/Unravel- amstatus-output-tf1953587.html#a5357597 Sent from the Amanda - Users forum at Nabble.com.
Re: RE Unravel amstatus output
Good point - and that is why I need help unravelling what it all means. My question now would be: 0.41% of what? What would 100% of that something represent? Constant streaming of data to tape from holding disk? I've just left it alone to see if I get different results when subsequently running amstatus, but it seems stuck at wherever it is at the moment. The tape drive itself is doing nothing... It really seems as if all went reasonably well and then froze up for some reason. Please help if at all possible. Cyrille Bollu wrote: Looking with my newbie's eyes it seems that Amanda is running well. Just very slowly. And Amanda's log seems to indicate that the problem is on the tape drive side. The only thing strange that I see is the following line which say that your drive is busy only 0,41% of the time: taper busy : 0:12:38 ( 0.41%) What does it do the rest of the time??? [EMAIL PROTECTED] a écrit sur 17/07/2006 10:54:55 : I set up Amanda on Friday to do an almost real backup job. I thought this would be the final test before putting it into operation. When I arrived at work this morning, I was somewhat surprised to see that the Amanda run doesn't seem to have finished. amstatus daily gives me some information, but I'm not sure how to interpret it. There are still 3 files on the holding disk, adding up to about 48GB. The tape drive doesn't seem to be doing anything - just sitting there quietly at the moment with no sign of activity. I won't include the entire output of amstatus daily, but here are extracts, if someone can please tell me if they see something wrong. I have many entries like these - seems to be one for each DLE: cerberus:/home 0 1003801k finished (22:18:15) Then these entries, which I think are the 2 that failed, as shown later in the summary: cerberus:/.autofsck 0 planner: [disk /.autofsck offline on cerberus?] cerberus:/.fonts.cache-1 0 planner: [disk /.fonts.cache-1 offline on cerberus?] Then these 3 that are the ones still on the holding disk: minerva:/home0 8774296k writing to tape (23:09:07) minerva:/usr/local/clients 0 32253287k dump done (1:08:27), wait for writing to tape minerva:/usr/local/development 0 9687648k dump done (23:48:17), wait for writing to tape And then this summary, which I'm not sure how to interpret: SUMMARY part real estimated size size partition : 109 estimated : 107 69631760k flush : 0 0k failed : 20k ( 0.00%) wait for dumping: 00k ( 0.00%) dumping to tape : 00k ( 0.00%) dumping : 0 0k 0k ( 0.00%) ( 0.00%) dumped : 107 58148656k 69631760k ( 83.51%) ( 83.51%) wait for writing: 2 41940935k 48107940k ( 87.18%) ( 60.23%) wait to flush : 0 0k 0k (100.00%) ( 0.00%) writing to tape : 1 8774296k 12515695k ( 70.11%) ( 12.60%) failed to tape : 0 0k 0k ( 0.00%) ( 0.00%) taped : 104 7433425k 9008125k ( 82.52%) ( 10.68%) 4 dumpers idle : not-idle taper writing, tapeq: 2 network free kps: 2000 holding space : 50295358k ( 49.79%) dumper0 busy : 2:53:47 ( 5.67%) dumper1 busy : 0:13:48 ( 0.45%) dumper2 busy : 0:00:00 ( 0.00%) taper busy : 0:12:38 ( 0.41%) 0 dumpers busy : 2+0:07:56 ( 94.22%)not-idle: 2+0:00:04 ( 99.73%) start-wait: 0:07:51 ( 0.27%) 1 dumper busy : 2:46:29 ( 5.43%)not-idle: 1:20:10 ( 48.15%) client-constrained: 1:18:08 ( 46.93%) no-bandwidth: 0:04:16 ( 2.57%) start-wait: 0:03:54 ( 2.35%) 2 dumpers busy : 0:10:34 ( 0.35%) client-constrained: 0:06:22 ( 60.27%) start-wait: 0:04:05 ( 38.76%) no-bandwidth: 0:00:06 ( 0.96%) 3 dumpers busy : 0:00:00 ( 0.00%) I would highly appreciate your insight into what is going on, especially for the 3 DLEs that are waiting for writing to tape. -- View this message in context: http://www.nabble.com/Unravel- amstatus-output-tf1953587.html#a5357597 Sent from the Amanda - Users forum at Nabble.com. -- View this message in context: http://www.nabble.com/Unravel-amstatus-output-tf1953587.html#a5358022 Sent from the Amanda - Users forum at Nabble.com.
Re: RE Unravel amstatus output
[EMAIL PROTECTED] a écrit sur 17/07/2006 11:36:21 : Good point - and that is why I need help unravelling what it all means. My question now would be: 0.41% of what? What would 100% of that something represent? Constant streaming of data to tape from holding disk? AFAIK, 100% would mean constant streaming. I've just left it alone to see if I get different results when subsequently running amstatus, but it seems stuck at wherever it is at the moment. The tape drive itself is doing nothing... It really seems as if all went reasonably well and then froze up for some reason. Yep, it looks like... Please help if at all possible. Cyrille Bollu wrote: Looking with my newbie's eyes it seems that Amanda is running well. Just very slowly. And Amanda's log seems to indicate that the problem is on the tape drive side. The only thing strange that I see is the following line which say that your drive is busy only 0,41% of the time: taper busy : 0:12:38 ( 0.41%) What does it do the rest of the time??? [EMAIL PROTECTED] a écrit sur 17/07/2006 10:54:55 : I set up Amanda on Friday to do an almost real backup job. I thought this would be the final test before putting it into operation. When I arrived at work this morning, I was somewhat surprised to see that the Amanda run doesn't seem to have finished. amstatus daily gives me some information, but I'm not sure how to interpret it. There are still 3 files on the holding disk, adding up to about 48GB. The tape drive doesn't seem to be doing anything - just sitting there quietly at the moment with no sign of activity. I won't include the entire output of amstatus daily, but here are extracts, if someone can please tell me if they see something wrong. I have many entries like these - seems to be one for each DLE: cerberus:/home 0 1003801k finished (22:18:15) Then these entries, which I think are the 2 that failed, as shown later in the summary: cerberus:/.autofsck 0 planner: [disk /.autofsck offline on cerberus?] cerberus:/.fonts.cache-1 0 planner: [disk /.fonts.cache-1 offline on cerberus?] Then these 3 that are the ones still on the holding disk: minerva:/home 0 8774296k writing to tape (23:09:07) minerva:/usr/local/clients 0 32253287k dump done (1:08:27), wait for writing to tape minerva:/usr/local/development 0 9687648k dump done (23:48:17), wait for writing to tape And then this summary, which I'm not sure how to interpret: SUMMARY part real estimated sizesize partition: 109 estimated: 107 69631760k flush : 0 0k failed : 2 0k ( 0.00%) wait for dumping: 0 0k ( 0.00%) dumping to tape : 0 0k ( 0.00%) dumping : 0 0k 0k ( 0.00%) ( 0.00%) dumped : 107 58148656k 69631760k ( 83.51%) ( 83.51%) wait for writing: 2 41940935k 48107940k ( 87.18%) ( 60.23%) wait to flush : 0 0k 0k (100.00%) ( 0.00%) writing to tape : 1 8774296k 12515695k ( 70.11%) ( 12.60%) failed to tape : 0 0k 0k ( 0.00%) ( 0.00%) taped : 104 7433425k 9008125k ( 82.52%) ( 10.68%) 4 dumpers idle : not-idle taper writing, tapeq: 2 network free kps: 2000 holding space : 50295358k ( 49.79%) dumper0 busy : 2:53:47 ( 5.67%) dumper1 busy : 0:13:48 ( 0.45%) dumper2 busy : 0:00:00 ( 0.00%) taper busy : 0:12:38 ( 0.41%) 0 dumpers busy : 2+0:07:56 ( 94.22%) not-idle: 2+0:00:04 ( 99.73%) start-wait: 0:07:51 ( 0.27%) 1 dumper busy : 2:46:29 ( 5.43%) not-idle: 1:20:10 ( 48.15%) client-constrained: 1:18:08 ( 46.93%) no-bandwidth: 0:04:16 ( 2.57%) start-wait: 0:03:54 ( 2.35%) 2 dumpers busy : 0:10:34 ( 0.35%) client-constrained: 0:06:22 ( 60.27%) start-wait: 0:04:05 ( 38.76%) no-bandwidth: 0:00:06 ( 0.96%) 3 dumpers busy : 0:00:00 ( 0.00%) I would highly appreciate your insight into what is going on, especially for the 3 DLEs that are waiting for writing to tape. -- View this message in context: http://www.nabble.com/Unravel- amstatus-output-tf1953587.html#a5357597 Sent from the Amanda - Users forum at Nabble.com. -- View this message in context: http://www.nabble.com/Unravel- amstatus-output-tf1953587.html#a5358022 Sent from the Amanda - Users forum at Nabble.com.
Re: RE Unravel amstatus output
On 2006-07-17 11:36, Joe Donner (sent by Nabble.com) wrote: Good point - and that is why I need help unravelling what it all means. My question now would be: 0.41% of what? What would 100% of that something represent? Constant streaming of data to tape from holding disk? of the total elapsed time since the program started. But there is some caveat. The amstatus command works by parsing the log file. And the logfile is written to only when there is a change in state in the backup process. So the 0.41% probably means that since the last status message written by taper in the logfile is already long ago. It could well be that taper is taping one very large file, but has not yet written that into the log file which amstatus parses. So, to find out if really anything is still running, do ps -fu amanda on the tape server, and verify if there is still a taper process (and other processes like driver). If they are, then what are they doing (strace -p help here). You may kill them all, and then clean up the broken pieces by running amcleanup. I've just left it alone to see if I get different results when subsequently running amstatus, but it seems stuck at wherever it is at the moment. The tape drive itself is doing nothing... It really seems as if all went reasonably well and then froze up for some reason. Please help if at all possible. Cyrille Bollu wrote: Looking with my newbie's eyes it seems that Amanda is running well. Just very slowly. And Amanda's log seems to indicate that the problem is on the tape drive side. The only thing strange that I see is the following line which say that your drive is busy only 0,41% of the time: taper busy : 0:12:38 ( 0.41%) What does it do the rest of the time??? [EMAIL PROTECTED] a écrit sur 17/07/2006 10:54:55 : I set up Amanda on Friday to do an almost real backup job. I thought this would be the final test before putting it into operation. When I arrived at work this morning, I was somewhat surprised to see that the Amanda run doesn't seem to have finished. amstatus daily gives me some information, but I'm not sure how to interpret it. There are still 3 files on the holding disk, adding up to about 48GB. The tape drive doesn't seem to be doing anything - just sitting there quietly at the moment with no sign of activity. I won't include the entire output of amstatus daily, but here are extracts, if someone can please tell me if they see something wrong. I have many entries like these - seems to be one for each DLE: cerberus:/home 0 1003801k finished (22:18:15) Then these entries, which I think are the 2 that failed, as shown later in the summary: cerberus:/.autofsck 0 planner: [disk /.autofsck offline on cerberus?] cerberus:/.fonts.cache-1 0 planner: [disk /.fonts.cache-1 offline on cerberus?] Then these 3 that are the ones still on the holding disk: minerva:/home0 8774296k writing to tape (23:09:07) minerva:/usr/local/clients 0 32253287k dump done (1:08:27), wait for writing to tape minerva:/usr/local/development 0 9687648k dump done (23:48:17), wait for writing to tape And then this summary, which I'm not sure how to interpret: SUMMARY part real estimated size size partition : 109 estimated : 107 69631760k flush : 0 0k failed : 20k ( 0.00%) wait for dumping: 00k ( 0.00%) dumping to tape : 00k ( 0.00%) dumping : 0 0k 0k ( 0.00%) ( 0.00%) dumped : 107 58148656k 69631760k ( 83.51%) ( 83.51%) wait for writing: 2 41940935k 48107940k ( 87.18%) ( 60.23%) wait to flush : 0 0k 0k (100.00%) ( 0.00%) writing to tape : 1 8774296k 12515695k ( 70.11%) ( 12.60%) failed to tape : 0 0k 0k ( 0.00%) ( 0.00%) taped : 104 7433425k 9008125k ( 82.52%) ( 10.68%) 4 dumpers idle : not-idle taper writing, tapeq: 2 network free kps: 2000 holding space : 50295358k ( 49.79%) dumper0 busy : 2:53:47 ( 5.67%) dumper1 busy : 0:13:48 ( 0.45%) dumper2 busy : 0:00:00 ( 0.00%) taper busy : 0:12:38 ( 0.41%) 0 dumpers busy : 2+0:07:56 ( 94.22%)not-idle: 2+0:00:04 ( 99.73%) start-wait: 0:07:51 ( 0.27%) 1 dumper busy : 2:46:29 ( 5.43%)not-idle: 1:20:10 ( 48.15%) client-constrained: 1:18:08 ( 46.93%) no-bandwidth: 0:04:16 ( 2.57%) start-wait: 0:03:54 ( 2.35%) 2 dumpers busy : 0:10:34 ( 0.35%) client-constrained: 0:06:22 ( 60.27%)
Re: RE Unravel amstatus output
Well, one thing I've noticed is that the DLEs in question are the ones with largest overall size: +/- 8GB +/- 9GB +/- 32GB All the other DLEs (except for the two I mentioned, which are in fact hidden files) have successfully been written to tape and are less than approximately 2GB in size... Cyrille Bollu wrote: [EMAIL PROTECTED] a écrit sur 17/07/2006 11:36:21 : Good point - and that is why I need help unravelling what it all means. My question now would be: 0.41% of what? What would 100% of that something represent? Constant streaming of data to tape from holding disk? AFAIK, 100% would mean constant streaming. I've just left it alone to see if I get different results when subsequently running amstatus, but it seems stuck at wherever it is at the moment. The tape drive itself is doing nothing... It really seems as if all went reasonably well and then froze up for some reason. Yep, it looks like... Please help if at all possible. Cyrille Bollu wrote: Looking with my newbie's eyes it seems that Amanda is running well. Just very slowly. And Amanda's log seems to indicate that the problem is on the tape drive side. The only thing strange that I see is the following line which say that your drive is busy only 0,41% of the time: taper busy : 0:12:38 ( 0.41%) What does it do the rest of the time??? [EMAIL PROTECTED] a écrit sur 17/07/2006 10:54:55 : I set up Amanda on Friday to do an almost real backup job. I thought this would be the final test before putting it into operation. When I arrived at work this morning, I was somewhat surprised to see that the Amanda run doesn't seem to have finished. amstatus daily gives me some information, but I'm not sure how to interpret it. There are still 3 files on the holding disk, adding up to about 48GB. The tape drive doesn't seem to be doing anything - just sitting there quietly at the moment with no sign of activity. I won't include the entire output of amstatus daily, but here are extracts, if someone can please tell me if they see something wrong. I have many entries like these - seems to be one for each DLE: cerberus:/home 0 1003801k finished (22:18:15) Then these entries, which I think are the 2 that failed, as shown later in the summary: cerberus:/.autofsck 0 planner: [disk /.autofsck offline on cerberus?] cerberus:/.fonts.cache-1 0 planner: [disk /.fonts.cache-1 offline on cerberus?] Then these 3 that are the ones still on the holding disk: minerva:/home0 8774296k writing to tape (23:09:07) minerva:/usr/local/clients 0 32253287k dump done (1:08:27), wait for writing to tape minerva:/usr/local/development 0 9687648k dump done (23:48:17), wait for writing to tape And then this summary, which I'm not sure how to interpret: SUMMARY part real estimated size size partition : 109 estimated : 107 69631760k flush : 0 0k failed : 20k ( 0.00%) wait for dumping: 00k ( 0.00%) dumping to tape : 00k ( 0.00%) dumping : 0 0k 0k ( 0.00%) ( 0.00%) dumped : 107 58148656k 69631760k ( 83.51%) ( 83.51%) wait for writing: 2 41940935k 48107940k ( 87.18%) ( 60.23%) wait to flush : 0 0k 0k (100.00%) ( 0.00%) writing to tape : 1 8774296k 12515695k ( 70.11%) ( 12.60%) failed to tape : 0 0k 0k ( 0.00%) ( 0.00%) taped : 104 7433425k 9008125k ( 82.52%) ( 10.68%) 4 dumpers idle : not-idle taper writing, tapeq: 2 network free kps: 2000 holding space : 50295358k ( 49.79%) dumper0 busy : 2:53:47 ( 5.67%) dumper1 busy : 0:13:48 ( 0.45%) dumper2 busy : 0:00:00 ( 0.00%) taper busy : 0:12:38 ( 0.41%) 0 dumpers busy : 2+0:07:56 ( 94.22%)not-idle: 2+0:00:04 ( 99.73%) start-wait: 0:07:51 ( 0.27%) 1 dumper busy : 2:46:29 ( 5.43%)not-idle: 1:20:10 ( 48.15%) client-constrained: 1:18:08 ( 46.93%) no-bandwidth: 0:04:16 ( 2.57%) start-wait: 0:03:54 ( 2.35%) 2 dumpers busy : 0:10:34 ( 0.35%) client-constrained: 0:06:22 ( 60.27%) start-wait: 0:04:05 ( 38.76%) no-bandwidth: 0:00:06 ( 0.96%) 3 dumpers busy :
Re: RE Unravel amstatus output
When I execute the top command (Red Hat Enterprise 3) for user Amanda, I get: PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND 2136 amanda15 0 948 948 836 S 0.0 0.0 0:00 1 amdump 2145 amanda15 0 1072 1072 844 S 0.0 0.1 0:02 1 driver 2146 amanda16 0 1536 1536 1388 S 0.0 0.1 0:52 0 taper 2147 amanda16 0 1560 1560 1396 D 0.0 0.1 0:34 0 taper 2148 amanda22 0 1120 1120 876 S 0.0 0.1 12:55 0 dumper 2153 amanda15 0 1120 1120 876 S 0.0 0.1 0:19 0 dumper 2154 amanda15 0 1044 1044 816 S 0.0 0.1 0:00 1 dumper 2155 amanda25 0 852 852 708 S 0.0 0.0 0:00 0 dumper and ps -fu amanda outputs: UIDPID PPID C STIME TTY TIME CMD amanda2136 2135 0 Jul14 ?00:00:00 /bin/sh /usr/sbin/amdump daily amanda2145 2136 0 Jul14 ?00:00:02 /usr/lib/amanda/driver daily amanda2146 2145 0 Jul14 ?00:00:52 taper daily amanda2147 2146 0 Jul14 ?00:00:34 taper daily amanda2148 2145 0 Jul14 ?00:12:55 dumper0 daily amanda2153 2145 0 Jul14 ?00:00:19 dumper1 daily amanda2154 2145 0 Jul14 ?00:00:00 dumper2 daily amanda2155 2145 0 Jul14 ?00:00:00 dumper3 daily Does this tell anyone anything? Paul Bijnens wrote: On 2006-07-17 11:36, Joe Donner (sent by Nabble.com) wrote: Good point - and that is why I need help unravelling what it all means. My question now would be: 0.41% of what? What would 100% of that something represent? Constant streaming of data to tape from holding disk? of the total elapsed time since the program started. But there is some caveat. The amstatus command works by parsing the log file. And the logfile is written to only when there is a change in state in the backup process. So the 0.41% probably means that since the last status message written by taper in the logfile is already long ago. It could well be that taper is taping one very large file, but has not yet written that into the log file which amstatus parses. So, to find out if really anything is still running, do ps -fu amanda on the tape server, and verify if there is still a taper process (and other processes like driver). If they are, then what are they doing (strace -p help here). You may kill them all, and then clean up the broken pieces by running amcleanup. I've just left it alone to see if I get different results when subsequently running amstatus, but it seems stuck at wherever it is at the moment. The tape drive itself is doing nothing... It really seems as if all went reasonably well and then froze up for some reason. Please help if at all possible. Cyrille Bollu wrote: Looking with my newbie's eyes it seems that Amanda is running well. Just very slowly. And Amanda's log seems to indicate that the problem is on the tape drive side. The only thing strange that I see is the following line which say that your drive is busy only 0,41% of the time: taper busy : 0:12:38 ( 0.41%) What does it do the rest of the time??? [EMAIL PROTECTED] a écrit sur 17/07/2006 10:54:55 : I set up Amanda on Friday to do an almost real backup job. I thought this would be the final test before putting it into operation. When I arrived at work this morning, I was somewhat surprised to see that the Amanda run doesn't seem to have finished. amstatus daily gives me some information, but I'm not sure how to interpret it. There are still 3 files on the holding disk, adding up to about 48GB. The tape drive doesn't seem to be doing anything - just sitting there quietly at the moment with no sign of activity. I won't include the entire output of amstatus daily, but here are extracts, if someone can please tell me if they see something wrong. I have many entries like these - seems to be one for each DLE: cerberus:/home 0 1003801k finished (22:18:15) Then these entries, which I think are the 2 that failed, as shown later in the summary: cerberus:/.autofsck 0 planner: [disk /.autofsck offline on cerberus?] cerberus:/.fonts.cache-1 0 planner: [disk /.fonts.cache-1 offline on cerberus?] Then these 3 that are the ones still on the holding disk: minerva:/home0 8774296k writing to tape (23:09:07) minerva:/usr/local/clients 0 32253287k dump done (1:08:27), wait for writing to tape minerva:/usr/local/development 0 9687648k dump done (23:48:17), wait for writing to tape And then this summary, which I'm not sure how to interpret: SUMMARY part real estimated size size partition : 109 estimated : 107 69631760k flush : 0 0k failed
Re: RE Unravel amstatus output
On 2006-07-17 13:32, Joe Donner (sent by Nabble.com) wrote: and ps -fu amanda outputs: UIDPID PPID C STIME TTY TIME CMD amanda2136 2135 0 Jul14 ?00:00:00 /bin/sh /usr/sbin/amdump daily amanda2145 2136 0 Jul14 ?00:00:02 /usr/lib/amanda/driver daily amanda2146 2145 0 Jul14 ?00:00:52 taper daily amanda2147 2146 0 Jul14 ?00:00:34 taper daily amanda2148 2145 0 Jul14 ?00:12:55 dumper0 daily amanda2153 2145 0 Jul14 ?00:00:19 dumper1 daily amanda2154 2145 0 Jul14 ?00:00:00 dumper2 daily amanda2155 2145 0 Jul14 ?00:00:00 dumper3 daily Does this tell anyone anything? It means the processes are still alive. Just a wild guess... Maybe you have specified a manual changer, and Amanda is just waiting for you to manually insert the next tape? Now find out what they are doing, and why it takes days to proceed. As root or amanda you can trace a process and see if it does somehting else, or is just sleeping on some event that will not happen: strace -p pid-of-the-process There are two taper processes, one reads from the holdingdisk file into a shared memory region, while the other one writes the bytes from shared memory to tape. When there is no holdingdisk file, then maybe the reader-taper is reading from a network socket? And maybe you specified a long dtimeout? -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: RE Unravel amstatus output
Red Hat Enterprise 3 doesn't seem to have strace as a command.
I thought rather than killing the processes manually, I'd reboot the server
and see if amcleanup runs as included in /etc/rc.d/rc.local (thought I may
as well test that).
Now the server came back up, and none of the amanda services are active
anymore (unsurprisingly). Nothing seemed to happen, so I did a manual
amcleanup, with these results:
amcleanup: no unprocessed logfile to clean up.
Scanning /mnt/hdb1...
20060714: found Amanda directory.
So I'm thinking that this backup run is now finally broken.
Next I thought I'll run amflush and see what happens. It outputs this:
Scanning /mnt/hdb1...
20060714: found Amanda directory.
Today is: 20060717
Flushing dumps in 20060714 to tape drive /dev/nst0.
Expecting tape daily-1 or a new tape. (The last dumps were to tape daily-3)
Are you sure you want to do this [yN]? y
Running in background, you can log off now.
You'll get mail when amflush is finished.
Now what I notice is that it asks for the tape called daily-1, whereas the
tape I used for Friday's backup was daily-3. Does this mean that daily-3
was filled up and caused this whole issue?
Which brings me to another question. I've used these tapes before for
testing. Will Amanda have appended Friday's backup to what was already on
the tape daily-3, or does it overwrite data previously written to that tape
each time a new backup runs? The reason I ask this is that the tape drive
capacity is 160GB, and I believe that I'm trying to back up a lot less data
than that.
After I rebooted, I got this email from Amanda. As you can see, it only
used 4.7% of the tape:
*** THE DUMPS DID NOT FINISH PROPERLY!
These dumps were to tape daily-3.
The next tape Amanda expects to use is: daily-1.
FAILURE AND STRANGE DUMP SUMMARY:
cerberus /.fonts.cache-1 lev 0 FAILED [disk /.fonts.cache-1 offline on
cerberus?]
cerberus /.autofsck lev 0 FAILED [disk /.autofsck offline on cerberus?]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:04
Run Time (hrs:min) 0:16
Dump Time (hrs:min)3:07 3:07 0:00
Output Size (meg) 56785.856785.80.0
Original Size (meg)136236.1 136236.10.0
Avg Compressed Size (%)41.7 41.7--
Filesystems Dumped 107107 0
Avg Dump Rate (k/s) 5169.8 5169.8--
Tape Time (hrs:min)0:13 0:13 0:00
Tape Size (meg) 7259.3 7259.30.0
Tape Used (%) 4.74.70.0
Filesystems Taped 104104 0
Avg Tp Write Rate (k/s) 9801.6 9801.6--
USAGE BY TAPE:
Label Time Size %Nb
daily-3 0:137259.34.7 104
And then, after I ran amflush, I got an email saying this (I didn't actually
put daily-1 into the drive):
*** A TAPE ERROR OCCURRED: [cannot overwrite active tape daily-3].
Some dumps may have been left in the holding disk.
Run amflush again to flush them to tape.
The next tape Amanda expects to use is: daily-1.
And when I now do amstatus daily, I get:
Using /var/lib/amanda/daily/amflush.1 from Mon Jul 17 12:58:42 BST 2006
minerva:/home 0 8774296k waiting to flush
minerva:/usr/local/clients 0 32253287k waiting to flush
minerva:/usr/local/development 0 9687648k waiting to flush
I feel a headache coming on again...
Any suggestions as how to best proceed?
Paul Bijnens wrote:
On 2006-07-17 13:32, Joe Donner (sent by Nabble.com) wrote:
and ps -fu amanda outputs:
UIDPID PPID C STIME TTY TIME CMD
amanda2136 2135 0 Jul14 ?00:00:00 /bin/sh /usr/sbin/amdump
daily
amanda2145 2136 0 Jul14 ?00:00:02 /usr/lib/amanda/driver
daily
amanda2146 2145 0 Jul14 ?00:00:52 taper daily
amanda2147 2146 0 Jul14 ?00:00:34 taper daily
amanda2148 2145 0 Jul14 ?00:12:55 dumper0 daily
amanda2153 2145 0 Jul14 ?00:00:19 dumper1 daily
amanda2154 2145 0 Jul14 ?00:00:00 dumper2 daily
amanda2155 2145 0 Jul14 ?00:00:00 dumper3 daily
Does this tell anyone anything?
It means the processes are still alive.
Just a wild guess... Maybe you have specified a manual changer, and
Amanda is just waiting for you to manually insert the next tape?
Now find out what they are doing, and why it takes days to proceed.
As root or amanda you can trace a process and see if it does somehting
else, or is just sleeping on some event that will not happen:
strace -p pid-of-the-process
There are two taper processes, one reads from the holdingdisk file
into a shared memory region, while the other one writes the bytes
from shared memory to tape. When there is no holdingdisk file, then
maybe the reader-taper is reading from a network socket?
And maybe
Difference between the amrestore and amrecover
HI, I need some clarification. I worked on amrestore , which we can retrieve the backup image from holding disk or tape. amrestore /dev/nst0 amrestore holdingdiskname But I didn't understand the amrecover. I feel amrecover is also developed for the same purpose. Why we need two commands for the restore? Is there any detailed technical mannual is available for amrecover? Please clarify the doubts. Thanks Regards, Silpakala __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: RE Unravel amstatus output
Ok, so I ran amflush again. It flushed 2 of the 3 outstanding DLE's data to
daily-1, but the email I received includes:
The dumps were flushed to tape daily-1.
The next tape Amanda expects to use is: daily-2.
FAILURE AND STRANGE DUMP SUMMARY:
minerva/usr/local/clients lev 0 FAILED [input: Can't read data: :
Input/output error]
And the holding disk still contains a folder with Friday's date and a 30GB
file for the DLE mentioned above.
What on earth is going on??
Joe Donner wrote:
Red Hat Enterprise 3 doesn't seem to have strace as a command.
I thought rather than killing the processes manually, I'd reboot the
server and see if amcleanup runs as included in /etc/rc.d/rc.local
(thought I may as well test that).
Now the server came back up, and none of the amanda services are active
anymore (unsurprisingly). Nothing seemed to happen, so I did a manual
amcleanup, with these results:
amcleanup: no unprocessed logfile to clean up.
Scanning /mnt/hdb1...
20060714: found Amanda directory.
So I'm thinking that this backup run is now finally broken.
Next I thought I'll run amflush and see what happens. It outputs this:
Scanning /mnt/hdb1...
20060714: found Amanda directory.
Today is: 20060717
Flushing dumps in 20060714 to tape drive /dev/nst0.
Expecting tape daily-1 or a new tape. (The last dumps were to tape
daily-3)
Are you sure you want to do this [yN]? y
Running in background, you can log off now.
You'll get mail when amflush is finished.
Now what I notice is that it asks for the tape called daily-1, whereas the
tape I used for Friday's backup was daily-3. Does this mean that daily-3
was filled up and caused this whole issue?
Which brings me to another question. I've used these tapes before for
testing. Will Amanda have appended Friday's backup to what was already on
the tape daily-3, or does it overwrite data previously written to that
tape each time a new backup runs? The reason I ask this is that the tape
drive capacity is 160GB, and I believe that I'm trying to back up a lot
less data than that.
After I rebooted, I got this email from Amanda. As you can see, it only
used 4.7% of the tape:
*** THE DUMPS DID NOT FINISH PROPERLY!
These dumps were to tape daily-3.
The next tape Amanda expects to use is: daily-1.
FAILURE AND STRANGE DUMP SUMMARY:
cerberus /.fonts.cache-1 lev 0 FAILED [disk /.fonts.cache-1 offline on
cerberus?]
cerberus /.autofsck lev 0 FAILED [disk /.autofsck offline on
cerberus?]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:04
Run Time (hrs:min) 0:16
Dump Time (hrs:min)3:07 3:07 0:00
Output Size (meg) 56785.856785.80.0
Original Size (meg)136236.1 136236.10.0
Avg Compressed Size (%)41.7 41.7--
Filesystems Dumped 107107 0
Avg Dump Rate (k/s) 5169.8 5169.8--
Tape Time (hrs:min)0:13 0:13 0:00
Tape Size (meg) 7259.3 7259.30.0
Tape Used (%) 4.74.70.0
Filesystems Taped 104104 0
Avg Tp Write Rate (k/s) 9801.6 9801.6--
USAGE BY TAPE:
Label Time Size %Nb
daily-3 0:137259.34.7 104
And then, after I ran amflush, I got an email saying this (I didn't
actually put daily-1 into the drive):
*** A TAPE ERROR OCCURRED: [cannot overwrite active tape daily-3].
Some dumps may have been left in the holding disk.
Run amflush again to flush them to tape.
The next tape Amanda expects to use is: daily-1.
And when I now do amstatus daily, I get:
Using /var/lib/amanda/daily/amflush.1 from Mon Jul 17 12:58:42 BST 2006
minerva:/home 0 8774296k waiting to flush
minerva:/usr/local/clients 0 32253287k waiting to flush
minerva:/usr/local/development 0 9687648k waiting to flush
I feel a headache coming on again...
Any suggestions as how to best proceed?
Paul Bijnens wrote:
On 2006-07-17 13:32, Joe Donner (sent by Nabble.com) wrote:
and ps -fu amanda outputs:
UIDPID PPID C STIME TTY TIME CMD
amanda2136 2135 0 Jul14 ?00:00:00 /bin/sh /usr/sbin/amdump
daily
amanda2145 2136 0 Jul14 ?00:00:02 /usr/lib/amanda/driver
daily
amanda2146 2145 0 Jul14 ?00:00:52 taper daily
amanda2147 2146 0 Jul14 ?00:00:34 taper daily
amanda2148 2145 0 Jul14 ?00:12:55 dumper0 daily
amanda2153 2145 0 Jul14 ?00:00:19 dumper1 daily
amanda2154 2145 0 Jul14 ?00:00:00 dumper2 daily
amanda2155 2145 0 Jul14 ?00:00:00 dumper3 daily
Does this tell anyone anything?
It means the processes are still alive.
Just a wild guess... Maybe you have specified a manual
Re: Difference between the amrestore and amrecover
On Mon, Jul 17, 2006 at 05:57:45AM -0700, silpa kala enlightened us: I need some clarification. I worked on amrestore , which we can retrieve the backup image from holding disk or tape. amrestore /dev/nst0 amrestore holdingdiskname But I didn't understand the amrecover. I feel amrecover is also developed for the same purpose. Why we need two commands for the restore? Is there any detailed technical mannual is available for amrecover? Please clarify the doubts. amrecover gives you an interactive interface to select specific files. amrestore is used for pulling entire DLE's from tape. There is a man page for amrecover and source code. What more do you need? Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263
Re: RE Unravel amstatus output
Joe Donner (sent by Nabble.com) wrote: FAILURE AND STRANGE DUMP SUMMARY: minerva/usr/local/clients lev 0 FAILED [input: Can't read data: : Input/output error] And the holding disk still contains a folder with Friday's date and a 30GB file for the DLE mentioned above. Can you try cat'ting the file to /dev/null? My first guess would be that some blocks of the holding disk file are unreadable due to a disk failure. Alex -- Alexander Jolk / BUF Compagnie tel +33-1 42 68 18 28 / fax +33-1 42 68 18 29
Re: RE Unravel amstatus output
Sorry, I've already went and deleted that file... Alexander Jolk wrote: Joe Donner (sent by Nabble.com) wrote: FAILURE AND STRANGE DUMP SUMMARY: minerva/usr/local/clients lev 0 FAILED [input: Can't read data: : Input/output error] And the holding disk still contains a folder with Friday's date and a 30GB file for the DLE mentioned above. Can you try cat'ting the file to /dev/null? My first guess would be that some blocks of the holding disk file are unreadable due to a disk failure. Alex -- Alexander Jolk / BUF Compagnie tel +33-1 42 68 18 28 / fax +33-1 42 68 18 29 -- View this message in context: http://www.nabble.com/Unravel-amstatus-output-tf1953587.html#a5361151 Sent from the Amanda - Users forum at Nabble.com.
Re: Port NNNN not secure (revisited)
Kevin Till wrote: Mike Allen wrote: After some helpful email from Frank Smith off-list I have decided to try a different approach to slve my problem: Here is an excerpt from my tape-server /etc/services file. amanda 20080/udp #Dump server control amandaidx 20082/tcp #Amanda indexing amidxtape 20083/tcp #Amanda tape indexing Note that I am not using the standard ports for amanda et al. A tcpdump from the client end of the communication between host 'familyserv' and host 'famrad' went as follows: snip 14:57:55.661773 IP familyserv.familyradio.org.ssh famrad.familyradio.org.44233: P 1048606257:1048606385(128) ack 4160186819 win 33304 nop,nop,timestamp 449488411 123825292 14:57:55.665181 IP famrad.familyradio.org.44233 familyserv.familyradio.org.ssh: . ack 128 win 33240 nop,nop,timestamp 123825301 449488402 14:58:06.382636 IP famrad.familyradio.org.34932 familyserv.familyradio.org.amanda: UDP, length: 119 14:58:06.423680 IP familyserv.familyradio.org.amanda famrad.familyradio.org.34932: UDP, length: 50 14:58:06.424676 IP familyserv.familyradio.org.amanda famrad.familyradio.org.34932: UDP, length: 109 14:58:06.428009 IP famrad.familyradio.org.34932 familyserv.familyradio.org.amanda: UDP, length: 50 Since both ends are supposedy configured for tcpportrange=512.1023 and udpportrange=5,50100 try configure with --with-tcpportrange=5,50100 --with-udpportrange=512,1023 ... and recompile. Open the corresponding ports in the firewall setup. The reason udp port 34932 was tried because Amanda cannot find a reserved udp port that it can use. The following occurred while compiling with the values you suggested: snip make install-data-hook chown operator /usr/local/man/man8/amanda.8 chgrp operator /usr/local/man/man8/amanda.8 chown operator /usr/local/man/man8/amanda.conf.5 chown: /usr/local/man/man8/amanda.conf.5: No such file or directory *** Error code 1 Stop in /usr/ports/misc/amanda-client/work/amanda-2.4.5p1/man. *** Error code 1 Stop in /usr/ports/misc/amanda-client/work/amanda-2.4.5p1/man. *** Error code 1 Stop in /usr/ports/misc/amanda-client/work/amanda-2.4.5p1/man. *** Error code 1 Stop in /usr/ports/misc/amanda-client/work/amanda-2.4.5p1. Why is it looking in /usr/local/man/man8 for a man5 manual page? I have seen this before. Mike
tape label report and tape spanning
I'm using the 3-hole label template. Amanda version is 2.5.0p2 from zmanda on Fedora 4. I'm taping to vtapes and tape spanning is turned on. Though I seldom exceed one tape the dumps are still split into tape_splitsize chunks. It appears to me that the File # column in the report is meaningless, except for the ordering of the dumps on the tape. The numbers simply increase by 2 for each DLE. So File #0 is the tape header, #2 is the first DLE dump, #4 is the second DLE etc. It doesn't matter if the DLE took 1 split or 50, the next File # is increased by 2. On physical tapes I would have expected these File #'s to allow me to mt fsf to that # and extract the dump I wanted. Clearly that is not the case for my reports. To confirm this I used ammt rewind and ammt fsf to advance to several file numbers. When I used amdd to read the vtape header it matched the 5 digit file numbers on disk rather than the File # from the printed report. Is it my misunderstanding of the report's File # or some problem generating the numbers? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Port NNNN not secure (revisited)
Mike Allen wrote: try configure with --with-tcpportrange=5,50100 --with-udpportrange=512,1023 ... and recompile. Open the corresponding ports in the firewall setup. The reason udp port 34932 was tried because Amanda cannot find a reserved udp port that it can use. The following occurred while compiling with the values you suggested: snip Hi, add -with-tcpportrange=5,50100 --with-udpportrange=512,1023 to whatever you have in your configure line. For example: ./configure --with-user=amandabackup --with-group=disk -with-tcpportrange=5,50100 --with-udpportrange=512,1023 Run configure again and make install. make install-data-hook chown operator /usr/local/man/man8/amanda.8 chgrp operator /usr/local/man/man8/amanda.8 chown operator /usr/local/man/man8/amanda.conf.5 chown: /usr/local/man/man8/amanda.conf.5: No such file or directory *** Error code 1 Stop in /usr/ports/misc/amanda-client/work/amanda-2.4.5p1/man. *** Error code 1 Stop in /usr/ports/misc/amanda-client/work/amanda-2.4.5p1/man. *** Error code 1 Stop in /usr/ports/misc/amanda-client/work/amanda-2.4.5p1/man. *** Error code 1 Stop in /usr/ports/misc/amanda-client/work/amanda-2.4.5p1. Why is it looking in /usr/local/man/man8 for a man5 manual page? I have seen this before. Mike -- Thank you! Kevin Till Amanda documentation: http://wiki.zmanda.com Amanda forums:http://forums.zmanda.com
Exact time and location for Amanda Birds of a Feather session at LinuxWorld in San Francisco in August
Hi all, If you plan attending upcoming LinuxWorld in San Francisco on August 14-17 or if you live in SF/Bay area, please stop by at Amanda Birds-of-a-Feather session on: Tuesday August 15, 2006, 6 - 7 p.m. BOF1: Open Source Backup and Recovery Software Amanda Room 301 The Amanda sessions we had at LinuxWorld in Boston and at MySQL user conference provided an excellent opportunity to meet other Amanda users, share experience and talk about Amanda's future. If you plan attending, could you please send me a note at [EMAIL PROTECTED] with suggestions what topics to cover in-depth from technical perspective. I will invite developers who work on Amanda to address your questions. Regards, Dmitri Joukovski * * * * * Come join the celebration of the 15th Anniversary of Linux at LINUXWORLD CONFERENCE EXPOR San Francisco August 14 - 17, 2006 - the ultimate Linux and open source gathering! LinuxWorld has assembled the best, most complete educational program in its history with over 100+ educational sessions, visionary keynotes, the latest open source technologies and non-stop special events - don't miss this event! For more information and to register, visit www.linuxworldexpo.com/sf
Re: Port NNNN not secure (revisited)
On Mon, Jul 17, 2006 at 09:32:01AM -0700, Mike Allen wrote: The following occurred while compiling with the values you suggested: snip make install-data-hook chown operator /usr/local/man/man8/amanda.8 chgrp operator /usr/local/man/man8/amanda.8 chown operator /usr/local/man/man8/amanda.conf.5 chown: /usr/local/man/man8/amanda.conf.5: No such file or directory *** Error code 1 Stop in /usr/ports/misc/amanda-client/work/amanda-2.4.5p1/man. *** Error code 1 Stop in /usr/ports/misc/amanda-client/work/amanda-2.4.5p1/man. *** Error code 1 Stop in /usr/ports/misc/amanda-client/work/amanda-2.4.5p1/man. *** Error code 1 Stop in /usr/ports/misc/amanda-client/work/amanda-2.4.5p1. Why is it looking in /usr/local/man/man8 for a man5 manual page? I have seen this before. That was a defect created when the man page for amanda.conf(5) was split from amanda(8). It was corrected in a later release. As I recall it was a very simple editing correction to the makefile(s) to do the installation. Otherwise manually install the manpages. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Port NNNN not secure (revisited)
Kevin Till wrote: Mike Allen wrote: try configure with --with-tcpportrange=5,50100 --with-udpportrange=512,1023 ... and recompile. Open the corresponding ports in the firewall setup. The reason udp port 34932 was tried because Amanda cannot find a reserved udp port that it can use. The following occurred while compiling with the values you suggested: snip Hi, add -with-tcpportrange=5,50100 --with-udpportrange=512,1023 to whatever you have in your configure line. For example: ./configure --with-user=amandabackup --with-group=disk -with-tcpportrange=5,50100 --with-udpportrange=512,1023 Run configure again and make install. make install-data-hook chown operator /usr/local/man/man8/amanda.8 chgrp operator /usr/local/man/man8/amanda.8 chown operator /usr/local/man/man8/amanda.conf.5 chown: /usr/local/man/man8/amanda.conf.5: No such file or directory *** Error code 1 Stop in /usr/ports/misc/amanda-client/work/amanda-2.4.5p1/man. *** Error code 1 Stop in /usr/ports/misc/amanda-client/work/amanda-2.4.5p1/man. *** Error code 1 Stop in /usr/ports/misc/amanda-client/work/amanda-2.4.5p1/man. *** Error code 1 Stop in /usr/ports/misc/amanda-client/work/amanda-2.4.5p1. Why is it looking in /usr/local/man/man8 for a man5 manual page? I have seen this before. Mike After configuring both the ta;e server and the client with the suggested portranges above I got the following: 14:46:02.501703 IP famrad.familyradio.org.47737 familyserv.familyradio.org.amanda: UDP, length: 123 14:46:02.543577 IP familyserv.familyradio.org.amanda famrad.familyradio.org.47737: UDP, length: 50 14:46:02.544603 IP familyserv.familyradio.org.amanda famrad.familyradio.org.47737: UDP, length: 109 14:46:02.549035 IP famrad.familyradio.org.47737 familyserv.familyradio.org.amanda: UDP, length: 50 Notice the reference to port 47737 which is outside the range(s) specified. I have a feeling I am doing something really stupid! Any help will be greatly appreciated. Mike
Re: Port NNNN not secure (revisited)
Mike Allen wrote: Kevin Till wrote: Mike Allen wrote: try configure with --with-tcpportrange=5,50100 --with-udpportrange=512,1023 ... and recompile. Open the corresponding ports in the firewall setup. The reason udp port 34932 was tried because Amanda cannot find a reserved udp port that it can use. The following occurred while compiling with the values you suggested: snip Hi, add -with-tcpportrange=5,50100 --with-udpportrange=512,1023 to whatever you have in your configure line. For example: ./configure --with-user=amandabackup --with-group=disk -with-tcpportrange=5,50100 --with-udpportrange=512,1023 Run configure again and make install. After configuring both the ta;e server and the client with the suggested portranges above I got the following: 14:46:02.501703 IP famrad.familyradio.org.47737 familyserv.familyradio.org.amanda: UDP, length: 123 14:46:02.543577 IP familyserv.familyradio.org.amanda famrad.familyradio.org.47737: UDP, length: 50 14:46:02.544603 IP familyserv.familyradio.org.amanda famrad.familyradio.org.47737: UDP, length: 109 14:46:02.549035 IP famrad.familyradio.org.47737 familyserv.familyradio.org.amanda: UDP, length: 50 Notice the reference to port 47737 which is outside the range(s) specified. I have a feeling I am doing something really stupid! Any help will be greatly appreciated. Is there a firewall in between? If it's iptables, you can tell by running iptables -L. The page below could be helpful too. http://wiki.zmanda.com/index.php/Configuration_with_iptables Mike -- Thank you! Kevin Till Amanda documentation: http://wiki.zmanda.com Amanda forums:http://forums.zmanda.com
Re: Port NNNN not secure (revisited)
On Mon, Jul 17, 2006 at 03:58:17PM -0700, Mike Allen wrote: Kevin Till wrote: Mike Allen wrote: try configure with --with-tcpportrange=5,50100 --with-udpportrange=512,1023 ... and recompile. Open the corresponding ports in the firewall setup. The reason udp port 34932 was tried because Amanda cannot find a reserved udp port that it can use. The following occurred while compiling with the values you suggested: snip Hi, add -with-tcpportrange=5,50100 --with-udpportrange=512,1023 to whatever you have in your configure line. For example: ./configure --with-user=amandabackup --with-group=disk -with-tcpportrange=5,50100 --with-udpportrange=512,1023 Run configure again and make install. After configuring both the ta;e server and the client with the suggested portranges above I got the following: 14:46:02.501703 IP famrad.familyradio.org.47737 familyserv.familyradio.org.amanda: UDP, length: 123 14:46:02.543577 IP familyserv.familyradio.org.amanda famrad.familyradio.org.47737: UDP, length: 50 14:46:02.544603 IP familyserv.familyradio.org.amanda famrad.familyradio.org.47737: UDP, length: 109 14:46:02.549035 IP famrad.familyradio.org.47737 familyserv.familyradio.org.amanda: UDP, length: 50 Notice the reference to port 47737 which is outside the range(s) specified. I have a feeling I am doing something really stupid! When you made your changes, before doing the configure, did you first do a make distclean? Then do your configure and make and make install. Configure caches some info and perhaps it is not resetting your portrange requests. I'm not sure where/which header they should be in, but you might check amanda.h under common-src. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Port NNNN not secure (revisited)
Kevin Till wrote: Mike Allen wrote: Kevin Till wrote: Mike Allen wrote: try configure with --with-tcpportrange=5,50100 --with-udpportrange=512,1023 ... and recompile. Open the corresponding ports in the firewall setup. The reason udp port 34932 was tried because Amanda cannot find a reserved udp port that it can use. The following occurred while compiling with the values you suggested: snip Hi, add -with-tcpportrange=5,50100 --with-udpportrange=512,1023 to whatever you have in your configure line. For example: ./configure --with-user=amandabackup --with-group=disk -with-tcpportrange=5,50100 --with-udpportrange=512,1023 Run configure again and make install. After configuring both the ta;e server and the client with the suggested portranges above I got the following: 14:46:02.501703 IP famrad.familyradio.org.47737 familyserv.familyradio.org.amanda: UDP, length: 123 14:46:02.543577 IP familyserv.familyradio.org.amanda famrad.familyradio.org.47737: UDP, length: 50 14:46:02.544603 IP familyserv.familyradio.org.amanda famrad.familyradio.org.47737: UDP, length: 109 14:46:02.549035 IP famrad.familyradio.org.47737 familyserv.familyradio.org.amanda: UDP, length: 50 Notice the reference to port 47737 which is outside the range(s) specified. I have a feeling I am doing something really stupid! Any help will be greatly appreciated. Is there a firewall in between? If it's iptables, you can tell by running iptables -L. The page below could be helpful too. http://wiki.zmanda.com/index.php/Configuration_with_iptables Mike Yes there is a firewall in between the tape-host and the client. It is NOT IP-tables based but is commercially made by Netgear. (That may be my problem). An assumption I am making is the path(s) from where I do my configurations. I'm using /usr/ports/.misc/amanda-client/work/amanda* and /usr/ports/misc/amanda-server/work/amanda* on the client and server respectively. Am I (re)configuring my system from the correct directory on my FreeBSD system? Mike
Re: Release of amanda-2.5.1b1
RPMs and source tar ball are available for following platforms at http://www.zmanda.com/downloads.html - Red Hat Enterprise server 4, - Red Hat Enterprise server 3 - Suse Linux Enterprise 9, - Suse Linux Enterprise 10, - Open Suse 10.0, - Fedora Core 3, - Fedora Core 4, - Fedora Core 5 and - Source RPM You can find the updated man pages and documentation in http://wiki.zmanda.com/ Any feedback on this beta release and wiki documentation would be appreciated. Thanks, Paddy On 7/14/06, Jean-Louis Martineau [EMAIL PROTECTED] wrote: Hello, The Amanda core team is pleased to announce the first beta release of Amanda 2.5.1, the 2.5.1b1 release. It can be dowloaded from http://www.amanda.org (not yet available) or https://sourceforge.net/project/showfiles.php?group_id=120 Here's a list of the changes for release 2.5.1b1 (from the NEWS file): Look at the ReleaseNotes and ChangeLog file for more details. * work with tar-1.15.91 * Open SSL encryption support * amfetchdump -o is replaced by -O. * amrecover_do_fsf default to yes * amrecover_check_label default to yes * amcheck -w will do all test including the tape writable test. use amcheck -t -w if you want only the tape writable test. * usetimestamps * bsdudp/bsdtcp, 2 new auth. * Unlimited number of DLE on a client with bsdtcp/rsh or ssh auth. * docs/howto-auth.txt * amandad_path, client_username and ssh_keys (for ssh/rsh) * client config file (see man amanda-client.conf) Only use by amrecover. * amrecover use the security-api * amoldrecover which use the old amindexd/amidxtaped protocol * -o option to overwrite config option (see in man amanda, the CONFIGURATION OVERWRITE section) If you find bug in this release, please submit a bug report on sourceforge in the group v2.5.1b1. (http://sourceforge.net/tracker/?group_id=120atid=100120) -- Amanda documentation: http://wiki.zmanda.com Amanda forums: http://forums.zmanda.com
Cyrille Bollu est absent(e).
Je serai absent(e) du 18/07/2006 au 01/08/2006. Je répondrai à votre message dès mon retour.
