Jira stopped write to log

Hello
JIRA suddenly stopped write to atlassian-jira.log and no new messages had appeared for two days, even after restart jira. The last messages were:


2015-04-01 13:03:12,677 localhost-startStop-2 INFO [atlassian.jira.startup.DefaultJiraLauncher] Stopping launchers
2015-04-01 13:03:12,701 localhost-startStop-2 INFO [atlassian.plugin.manager.DefaultPluginManager] Shutting down the plugin system
2015-04-01 13:03:13,016 Timer-2 INFO [greenhopper.service.logging.LogSupport]
*********************************************************************************
Atlassian GreenHopper v6.6.13 #8178361f26f6d33d built 2014-11-05T09:53:38.428+04:00 - plugin stopping...
*********************************************************************************
2015-04-01 13:03:13,021 Timer-2 WARN [atlassian.greenhopper.service.BridgeServiceLocator] The GreenHopper BridgeServiceLocator has been unwired and is no longer usable
2015-04-01 13:03:13,021 Timer-2 INFO [greenhopper.service.logging.LogSupport]
*********************************************************************************
Atlassian GreenHopper v6.6.13 #8178361f26f6d33d built 2014-11-05T09:53:38.428+04:00 - plugin stopped
*********************************************************************************
2015-04-01 13:03:13,243 Timer-2 WARN [timesheet.plugin.job.TimesheetJobScheduler] Can't unschedule timesheet job: The Scheduler has been shutdown.
2015-04-01 13:03:13,243 Timer-2 WARN [timesheet.plugin.job.TimesheetJobScheduler] Can't delete timesheet job: The Scheduler has been shutdown.

The last error-message:

2015-04-01 13:03:12,672 atlassian-scheduler-quartz1.local_Worker-3 ERROR ServiceRunner [org.quartz.core.JobRunShell] Job SchedulerServiceJobs.com.atlassi
an.jira.service.DefaultServiceManager threw an unhandled Exception:
com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: Unable to establish a connection with the database. (Communications link failure The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.)

What could be the reason that JIRA stopped write to log-file? I did not  made any changes in logging and profiling section, the last changes I've done - I replace the old mysql-driver to new version because mysql was upgraded recently. 

1 answer

2 votes

Is the log file large?  Should it have been rotated?  Is the disk full?  Simple trick is to stop Jira, rename or move the log file and restart JIRA - that should make a new, clean one.

The last error message in the log is a bit of a scary one too - it means you've got problems with the database connection, and that often stops JIRA dead, as well as potentially corrupting data

Thank you! File was large but not very. I moved the log file to another directory and after restart Jira it created the new log file, and all seems ok with this.

If you change the db driver you should restart Jira anyway

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Oct 16, 2018 in Jira

Looking for anyone who made the switch to Data Center

The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...

63 views 0 2
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you