Ahsay Discussion Forum

[littlefish]

Hello

When I go to Manage Log -> Backup Job, the list does not appear to have updated since 2nd Feb 2010.
I am running OBM Version 5.5.3.2 and there has definetly been several backup jobs since 2nd Feb 2010.

What could be causing the list to stop updating with recent jobs/dates?

Regards
-Littlefish

[Support3]

Can you verify under the system log (Manage Log -> System Log) and see if there is any error messages shown? Furthermore, please also verify if there is any error found within the catalina and context logs found at: ${Install-Home}\logs

Thanks.

[backithere]

Dumb question, but have to ask.....is there plenty of disk space where the logs are?

I run OBS on a VM with 20GB of space. I was told by support that this was plenty of room for logs; however, recently I haven't been able to keep more then 30 days because of the size of the logs.

[drool]

The backups were probably run from a different HOME then the user you were logged in as, so the logs may be stored in the .obm directory of another user. Check the scheduler log in the OBM install directory (\log\scheduler\info.log) and see what HOME the scheduler was launched with. You may also check the home.txt file and see if there are multiple entries. This whole multiple entires in the home.txt (auto popluated and added to by any user who launches the OBM client) is a design "feature" that has caused me countless headaches.

The way I've solved this problem is by removing all but the one entry I want in the home.txt, then setting the home.txt file to read-only so no other entries can be added.

[littlefish]

Hi,
Thanks for all the reponses.

We have 1.4Gb of free space.

The last catalina log from the 3rd Feb reads :

Feb 2, 2010 11:46:46 PM org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler process
SEVERE: Error reading request, ignored
java.lang.OutOfMemoryError: Java heap space
Feb 3, 2010 12:14:55 AM org.apache.catalina.connector.CoyoteAdapter service
SEVERE: An exception or error occurred in the container during the request processing
java.lang.OutOfMemoryError: Java heap space
Feb 3, 2010 12:25:06 AM org.apache.catalina.connector.CoyoteAdapter service
SEVERE: An exception or error occurred in the container during the request processing
java.lang.OutOfMemoryError: Java heap space
Feb 3, 2010 1:00:14 AM org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler process
SEVERE: Error reading request, ignored
java.lang.OutOfMemoryError: Java heap space
Feb 3, 2010 12:46:37 AM org.apache.catalina.connector.CoyoteAdapter service
SEVERE: An exception or error occurred in the container during the request processing
java.lang.OutOfMemoryError: Java heap space
Feb 3, 2010 1:00:14 AM org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler process
SEVERE: Error reading request, ignored
java.lang.OutOfMemoryError: Java heap space
Feb 3, 2010 12:46:37 AM org.apache.catalina.connector.CoyoteAdapter service
SEVERE: An exception or error occurred in the container during the request processing
java.lang.OutOfMemoryError: Java heap space
Feb 3, 2010 12:47:19 AM org.apache.catalina.connector.CoyoteAdapter service
SEVERE: An exception or error occurred in the container during the request processing
java.lang.OutOfMemoryError: Java heap space
Feb 3, 2010 12:02:01 AM org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler process
SEVERE: Error reading request, ignored
java.lang.OutOfMemoryError: Java heap space
Feb 3, 2010 12:32:51 AM org.apache.tomcat.util.net.JIoEndpoint$Acceptor run
SEVERE: Socket accept failed
java.lang.OutOfMemoryError: Java heap space
Feb 3, 2010 12:00:14 AM org.apache.catalina.connector.CoyoteAdapter service
SEVERE: An exception or error occurred in the container during the request processing
java.lang.OutOfMemoryError: Java heap space


Looking at this prompts me to tell you that on the 2nd we also changed the java heap size from default to -Xmx1200m.

I hope this helps.

[Support3]

From the error messages, it suggests that the memory allocated for the AhsayOBS server is not sufficient for the backup operation. However, as you mentioned that you had increased the Java heap size for the AhsayOBS server, may I ask if the "heap size" error is resolved afterward?

Regarding the new backup job not showing on the AhsayOBS management console, can you verify under the following location:
${System-Home}\system\BackupJob

Check to see if there is any updated entries within the folder.

Thanks.

[littlefish]

I updated the java heap size due to a java heap size error on a win2k8 server backing up SQL.
This did not resolve the java heap size error on that particular schedule and we have plans to upgrade to 5.5.5 which references java heap size fix.

The logs appear to have stopped after I increased the heap size.

Just for clarification, the logs we refer to are the administrator summary view of all schedules for a particular day. Manage Log -> Backup Job.

The following folder is in the directory you refer too.
2009-09-04
which holds the following files.
2009-09-04-11-17-42+1252059235570+test.log
2009-09-04-11-20-00+1252059235570+test.log

Thanks

[Support3]

Yes, we are aware of the location of log you are referring to.

Can I ask if you have changed you system home location? The previous directory path that we have suggested is the location where the backup job log is stored on the AhsayOBS server (for OBS's reference to the job performed on each date). It is strange that the location only contain log files from Sept 04 of last year.

To further investigate in this issue, we may require access to your server in order to isolate the problem. Can you please submit a Support Ticket for us to further assist you?

Thanks.