confluence stops working after a couple of days

[marius]

Hi,

I installed Confluence on my Ubuntu vps, and for a month or two it stops working every couple of days.If I look into atlassian-confluence.log I find this kind of error

2019-06-02 02:58:33,374 WARN [HealthCheck:thread-1] [troubleshooting.stp.spi.DefaultFileSystemInfo] lambda$getThreadLimit$0 Failed to determine the configured process limit
java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Integer.java:542)
at java.lang.Integer.parseInt(Integer.java:615)
at com.atlassian.troubleshooting.stp.spi.DefaultFileSystemInfo.lambda$getThreadLimit$0(DefaultFileSystemInfo.java:52)

[Soporte Excentia · Accepted solution]

Hi Marius :)

This problem seems to be related with the number of threads Confluence can run at same time. 

In the following KB article you cand find a possible resolution. You should change yout limits.conf file.

https://confluence.atlassian.com/kb/health-check-thread-limit-858578685.html

Best regards.

[Deleted user]

thank you. updated limits.conf. Will reply in a couple of days with the result.

[Deleted user]

hey again. That did not work.

Searched all for all files named limits.conf, there is only one in /etc/security. Checked to see if I edited correctly and it looks like this:

...

#        - stack - max stack size (KB)

#        - cpu - max CPU time (MIN)

#        - nproc - max number of processes

#        - as - address space limit (KB)

#        - maxlogins - max number of logins for this user

#        - maxsyslogins - max number of logins on the system

#        - priority - the priority to run user process with

#        - locks - max number of file locks the user can hold

#        - sigpending - max number of pending signals

#        - msgqueue - max memory used by POSIX message queues (bytes)

#        - nice - max nice priority allowed to raise to values: [-20, 19]

#        - rtprio - max realtime priority

#        - chroot - change root to directory (Debian-specific)

#

#<domain>      <type>  <item>         <value>

#




#*               soft    core            0

#root            hard    core            100000

#*               hard    rss             10000

#@student        hard    nproc           20

#@faculty        soft    nproc           20

#@faculty        hard    nproc           50

#ftp             hard    nproc           0

#ftp             -       chroot          /ftp

#@student        -       maxlogins       4




confluence      soft   nofile  4096

confluence      hard   nofile  8192

confluence      soft   nproc   4096

confluence      hard   nproc   8192




# End of file

The next step would be to find out what log files I should clear, restart confluence, and check to see the errors. Can you tell me the names of the log files ?

[Soporte Excentia]

Hi Marius!

I am sorry to hear that it did not work :(

The log files you should check are normally located in. In these files you should find the cause of 90% of Confluence app problems.

/var/atlassian/application-data/confluence/log/atlassian-confluence.log

/opt/atlassian/confluence/logs/catalina.out

Did you try to restart your server after changing limits.conf? (Restart after changing limits.conf) I would like to recommend  you to read this thread.

By the way, could you browse this URL BASE_URL/plugins/servlet/troubleshooting/view/ and tell me what you see? Are all items checked?

Also, if Confluence stops again, please provide and extract of last lines of those log files. 

See you!

[Deleted user]

hey again. there are the logs:

https://www.dropbox.com/s/ewvl16dwu8f9ybr/atlassian-confluence.log?dl=0

https://www.dropbox.com/s/dmcz7ziull1kpay/atlassian-synchrony.log?dl=0

https://www.dropbox.com/s/a9icnhbp5rgbr8v/catalina.out?dl=0

limits.conf did not work. do you mean restarting the whole vps ? or just confluence ?

URL BASE_URL/plugins/servlet/troubleshooting/view/  shows the same message:

Service Unavailable

The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

Additionally, a 503 Service Unavailable error was encountered while trying to use an ErrorDocument to handle the request.

[marius]

hey. iti seems the limits.conf worked after I restarted my vps. 

thank you @Soporte Excentia  !!!!

[Soporte Excentia]

Great @[deleted] ! I am really happy to read this :)

Thanks for your feedback.