ERROR: Unable to archive data file already exists|
This error indicates that archiving is unable to run because a previous archive process was stopped before successful completion. An example error message from the uptime.log file is included below. To correct this problem, simply delete the indicated file and let archiving run as scheduled. Please contact uptime Support if the error persists.
2010-05-30 02:33:36,968 ERROR (ArchiveDataRunner:44) - Unable to archive data: java.lang.RuntimeException: Can not archive data, file archives\performance_fscap_2010-03-01.xml.gz already exists at com.uptimesoftware.uptime.archiving.PerformanceDataDumper.outputDataFromTables(PerformanceDataDumper.java:40) at com.uptimesoftware.uptime.archiving.PerformanceDataDumper.dump(PerformanceDataDumper.java:22) at com.uptimesoftware.uptime.archiving.ArchiveDataRunner.dumpData(ArchiveDataRunner.java:90) at com.uptimesoftware.uptime.archiving.ArchiveDataRunner.dumpAndScheduleDeletion(ArchiveDataRunner.java:51) at com.uptimesoftware.uptime.archiving.ArchiveDataRunner.executePolicy(ArchiveDataRunner.java:41) at com.uptimesoftware.uptime.archiving.ArchiveDataRunner.archive(ArchiveDataRunner.java:30) at com.uptimesoftware.uptime.archiving.ArchiveDataTask$1.save(ArchiveDataTask.java:50) at com.uptimesoftware.uptime.database.Saver.save(Saver.java:11) at com.uptimesoftware.uptime.archiving.ArchiveDataTask.run(ArchiveDataTask.java:53) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source) at java.util.concurrent.FutureTask.runAndReset(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) |
Article InfoIndex: 443 OptionsQuick Links |
Agent rpm install error: unpacking of archive failed on file | Rating | Views | |
|---|---|---|---|
|
|
At times during the installation of up.time's rpm based agents (Linux and ESX 2) you may receive a 'file size' error. This error is usually a result of a bad file download. It is suggested that you... By: uptime Support | Date Created: 10-10-2009 | Last Modified: 8-10-2011 | Index: 406 |
 
|
3466 |
Importing Archived Data into up.time | Rating | Views | |
|---|---|---|---|
|
By: uptime Support | Date Created: 6-9-2006 | Last Modified: 8-9-2011 | Index: 076 |
|
4129 |
SMTP Error 550 5.7.1 Unable to relay | Rating | Views | |
|---|---|---|---|
|
|
At times you may notice an error in the uptime.log or alert profile test function indicating that up.time was unable to send mail to a specific email address. An example of the error message is... By: uptime Support | Date Created: 10-10-2009 | Last Modified: 8-13-2011 | Index: 421 |
|
12001 |
Error: Unable to contact agent | Rating | Views | |
|---|---|---|---|
|
|
When adding a new element to up.time this error indicates that the monitoring station was unable to contact the target agent using the IP,Port & SSL information you have entered. Generally the... By: uptime Support | Date Created: 8-4-2010 | Last Modified: 8-13-2011 | Index: 460 |
|
2587 |
'up.time Data Collector is unavailable' error in web interface | Rating | Views | |
|---|---|---|---|
|
|
If you have recently changed the hostname of your monitoring station and receive the message "Database Not Responding" in the monitoring station web interface, you must make the following... By: uptime Support | Date Created: 10-1-2009 | Last Modified: 10-18-2013 | Index: 379 |
|
3469 |
