Jira stopped write to log

[Elena Oleksenko]

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. 

[Nic Brough -Adaptavist-]

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

[Elena Oleksenko]

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.

[MattS]

If you change the db driver you should restart Jira anyway