T.R | Title | User | Personal Name | Date | Lines |
---|
906.1 | | 29067::BUTTERWORTH | Gun Control is a steady hand. | Fri Aug 04 1995 15:42 | 14 |
| is it possible for us to access the SYSTEM when the archive is hung?
The ECO fixed a problem where the daemons would hang when an archive
was done but this sounds like a different problem.
As far as your file access conflicts go... was there a backup running
at the same time? That error indicates that something had the files
locked at the time. V1.6 will not perform an archive if someone is
connected and the problem where the controller daemon didn't close the
file was also fixed. This leaves some other extraneous source like
BACKUP.
Regards,
Dan
|
906.2 | Contact | 45213::BRODIE | | Mon Aug 07 1995 04:52 | 10 |
| Access,
No problem.. I will mail you contact details....
Backups running, None have ever been run during the archieve period. It
may be posible that someone was connected. Concern from site thou' is
that assuming somebody was connected, then why does archieve now fall
over stone dead, under v1.5 it would only fail the one event then carry
on as before?
Alan Brodie/
|
906.3 | similar archive problem | 50242::MUELLER | | Tue Aug 08 1995 06:33 | 39 |
| Hi,
just want to let you know that I got a similar problem with my
archive procedure...
command:
console archive/before=today/noconfirm all
logfile:
Archive procedure for system GYDNS completed successfully
Starting archive procedure for system GYHUB
Timefile Pass 1: Working ... done.
Timefile Pass 2: Working ... done.
Logfile Pass 1: Working ... done.
Logfile Pass 2: Working ... done.
Eventfile Pass 1: Working ... done.
Updating Pass 1: Working ... done.
Archive procedure for system GYHUB completed successfully
Starting archive procedure for system GYMAC
Archive area is full - archive procedure for system GYMAC failed
Starting archive procedure for system GYMRC0
Log file open failure for GYMRC0
acp file access failed
Archive for system GYMRC0 complete - log file is empty
Starting archive procedure for system GYMRC1
Log file open failure for GYMRC1
acp file access failed
The archive area is not full - free blocks: 5646200
total blocks: 6976375
File space warning threshold = 80% full
File space critical threshold = 95% full
Regards,
- Sabine
|
906.4 | | 29067::BUTTERWORTH | Gun Control is a steady hand. | Tue Aug 08 1995 13:55 | 17 |
| Re -2.
Something had the files locked. Archive was changed dramatically in
V1.6 as there were to many problems in the old V1.5 code stream. If
someone was connected, you would have gotten a message to the effect
Archive aborted - user xxxxxxx is connected
and it would have attempted to archive the next system.
Is there a disk defragger running on this system?
Regs,
Dan
|
906.5 | No defrag | 45213::BRODIE | | Wed Aug 09 1995 07:30 | 5 |
| Dan
Certainly in my case there is NOT a defrag process running.
ALan Brodie/
|
906.6 | BYTLM | 42441::JUDD | Geoff Judd. UK TSC. Viables, Basingstoke | Tue Aug 15 1995 13:12 | 5 |
| I can reproduce this problem by reducing my BYTLM quota. All the quota is given
back at the end of the archive run but the amount used increases each time a new
node is archived.
Geoff Judd.
|
906.7 | | 29067::BUTTERWORTH | Gun Control is a steady hand. | Tue Aug 15 1995 15:11 | 4 |
| Thats great info Geoff!! Good job!!
Regs,
Dan
|
906.8 | now it works... | 50242::MUELLER | | Wed Aug 16 1995 11:14 | 7 |
| I just raised the bytlm quota and the archive works fine.
Thanks a lot!
Regards,
- Sabine
|