Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Atlassian Fisheye service not starting in windows sever 2016 - error "Commons Daemon procrun failed"

Kiran Kumar Madala
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 8, 2024

HI ,

We are using fisheye version : 4.8.6
Few days back DB migrated, after application was working fine , but suddenly service stopped and unable to start the server.
From Logs , we can see below error. 

[error] [ 4664] Failed to start 'Atlassian Fisheye' service [error] [ 4664] The data area passed to a system call is too small. [error] [ 4664] Commons Daemon procrun failed with exit value: 5 (Failed to start service) [error] [ 4664] The data area passed to a system call is too small.

Thanks,

1 answer

0 votes
Mirek
Community Champion
May 31, 2025

Would be nice to know more details - what operating system, what database.. but looking overall at this problem it is probably related to some system problem rather than application itself.. 

I would start with checking all limits (memory, number of open files on the operating system or JVM settings - heap size etc. .. ) 

If this was a database migration the carefully review all the configuration.. maybe new database is not officially compatible with this specific version? Or something simple like no permission to specific files or lack of disc space.. 

However Daemon Procrun failed usually is related with services (how the service is being started, or it may not have the required permissions)

Rrunning the Fisheye service manually might help or restarting the service. If on Windows, it may be worth verifying the "Fisheye" service configuration and permissions.

 

 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events