Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse

Cloudron Forum

Apps | Demo | Docs | Install

Anyone having the OnlyOffice 7 update "not responding"?

Scheduled Pinned Locked Moved Solved OnlyOffice
not workingupdateonlyoffice
10 Posts 5 Posters 311 Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • scookeS Offline
    scookeS Offline
    scooke
    wrote on last edited by
    #1

    It updated, then failed to start and was listed as Not Responding. I restored to a v 1.95.0 backup thankfully so it's running again. I'll give it another go again, but if someone else has had an issue and fixed it, that would potentially be of great help!

    A life lived in fear is a life half-lived

    timconsidineT 1 Reply Last reply
    0
  • girishG Offline
    girishG Offline
    girish Staff
    wrote on last edited by
    #2

    FWIW, our internal instance updated fine. Did you see anything in the logs? BTW, the 'not responding' could also be a symptom of the box code cron having problems. You can do systemctl restart box just to double check . There is some issue in the cron module which when run over many days sometimes stops working. This causes the internal healthcheck polling code to not run and thus not update the app state as 'running'.

    scookeS 1 Reply Last reply
    1
  • scookeS Offline
    scookeS Offline
    scooke
    replied to girish on last edited by
    #3

    @girish I'll try again and keep a close eye on the logs. Maybe I'll even restart the whole server beforehand, just to be sure everything is running well.

    A life lived in fear is a life half-lived

    1 Reply Last reply
    0
  • jdaviescoatesJ Offline
    jdaviescoatesJ Offline
    jdaviescoates
    wrote on last edited by
    #4

    Mine has updated fine, no issues.

    I use Cloudron with Gandi & Hetzner

    1 Reply Last reply
    0
  • scookeS Offline
    scookeS Offline
    scooke
    wrote on last edited by
    #5

    Welp, the update went well, but now when I click on a file in the Files view it initiates a download. I think I will go back to CODE.

    A life lived in fear is a life half-lived

    nebulonN 1 Reply Last reply
    0
  • nebulonN Offline
    nebulonN Offline
    nebulon Staff
    replied to scooke on last edited by
    #6

    @scooke if a download is triggered, then I think this is a content-type issue in nextcloud. Maybe check the file types configured for the connector plugin?

    scookeS 1 Reply Last reply
    0
  • scookeS Offline
    scookeS Offline
    scooke
    replied to nebulon on last edited by
    #7

    @nebulon I went in to the Settings in NC and assigned everything.
    Right now it "works", but is slow as molasses . Too bad, I was looking forward to the goodies in the V7 upgrade.

    A life lived in fear is a life half-lived

    scookeS 1 Reply Last reply
    0
  • scookeS Offline
    scookeS Offline
    scooke
    replied to scooke on last edited by
    #8

    I restored to version 9.5.0 and it was working. Sometime in the last 3 days it auto-updated to v1.10.0 and it is not responding again. This might be pertinent:

    Jan 26 08:40:00 204.187.100.82 - - [26/Jan/2022:07:40:00 +0000] "GET /apps/photos/service-worker.js HTTP/1.1" 200 4828 "https://nextcloud.domain.com/apps/photos/service-worker.js" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.99 Safari/537.36"
    Jan 26 07:27:38 16:M 26 Jan 2022 06:27:38.375 * Background saving terminated with success
    Jan 26 07:32:39 16:M 26 Jan 2022 06:32:39.035 * 10 changes in 300 seconds. Saving...
    Jan 26 07:32:39 16:M 26 Jan 2022 06:32:39.036 * Background saving started by pid 3917
    Jan 26 07:32:39 3917:C 26 Jan 2022 06:32:39.284 * DB saved on disk
    Jan 26 07:32:39 3917:C 26 Jan 2022 06:32:39.287 * RDB: 0 MB of memory used by copy-on-write
    Jan 26 07:32:39 16:M 26 Jan 2022 06:32:39.338 * Background saving terminated with success
    Jan 26 07:37:40 16:M 26 Jan 2022 06:37:40.015 * 10 changes in 300 seconds. Saving...
    Jan 26 07:37:40 16:M 26 Jan 2022 06:37:40.018 * Background saving started by pid 3918
    Jan 26 07:37:40 3918:C 26 Jan 2022 06:37:40.358 * DB saved on disk
    Jan 26 07:37:40 3918:C 26 Jan 2022 06:37:40.360 * RDB: 1 MB of memory used by copy-on-write
    Jan 26 07:37:40 16:M 26 Jan 2022 06:37:40.421 * Background saving terminated with success
    Jan 26 07:42:41 16:M 26 Jan 2022 06:42:41.096 * 10 changes in 300 seconds. Saving...
    Jan 26 07:42:41 16:M 26 Jan 2022 06:42:41.098 * Background saving started by pid 3919
    Jan 26 07:42:41 3919:C 26 Jan 2022 06:42:41.346 * DB saved on disk
    Jan 26 07:42:41 3919:C 26 Jan 2022 06:42:41.349 * RDB: 0 MB of memory used by copy-on-write
    Jan 26 07:42:41 16:M 26 Jan 2022 06:42:41.399 * Background saving terminated with success
    Jan 26 07:47:42 16:M 26 Jan 2022 06:47:42.000 * 10 changes in 300 seconds. Saving...
    Jan 26 07:47:42 16:M 26 Jan 2022 06:47:42.002 * Background saving started by pid 3920
    Jan 26 07:47:42 3920:C 26 Jan 2022 06:47:42.211 * DB saved on disk
    Jan 26 07:47:42 3920:C 26 Jan 2022 06:47:42.212 * RDB: 0 MB of memory used by copy-on-write
    Jan 26 07:47:42 16:M 26 Jan 2022 06:47:42.304 * Background saving terminated with success
    Jan 26 07:52:43 16:M 26 Jan 2022 06:52:43.094 * 10 changes in 300 seconds. Saving...
    Jan 26 07:52:43 16:M 26 Jan 2022 06:52:43.097 * Background saving started by pid 3921
    Jan 26 07:52:43 3921:C 26 Jan 2022 06:52:43.316 * DB saved on disk
    Jan 26 07:52:43 3921:C 26 Jan 2022 06:52:43.317 * RDB: 0 MB of memory used by copy-on-write
    Jan 26 07:52:43 16:M 26 Jan 2022 06:52:43.398 * Background saving terminated with success
    Jan 26 07:57:44 16:M 26 Jan 2022 06:57:44.016 * 10 changes in 300 seconds. Saving...
    Jan 26 07:57:44 16:M 26 Jan 2022 06:57:44.018 * Background saving started by pid 3922
    Jan 26 07:57:44 3922:C 26 Jan 2022 06:57:44.239 * DB saved on disk
    Jan 26 07:57:44 3922:C 26 Jan 2022 06:57:44.241 * RDB: 0 MB of memory used by copy-on-write
    Jan 26 07:57:44 16:M 26 Jan 2022 06:57:44.320 * Background saving terminated with success
    Jan 26 08:02:45 16:M 26 Jan 2022 07:02:45.027 * 10 changes in 300 seconds. Saving...
    Jan 26 08:02:45 16:M 26 Jan 2022 07:02:45.029 * Background saving started by pid 3923
    Jan 26 08:02:45 3923:C 26 Jan 2022 07:02:45.272 * DB saved on disk
    Jan 26 08:02:45 3923:C 26 Jan 2022 07:02:45.274 * RDB: 0 MB of memory used by copy-on-write
    Jan 26 08:02:45 16:M 26 Jan 2022 07:02:45.330 * Background saving terminated with success
    Jan 26 08:07:46 16:M 26 Jan 2022 07:07:46.053 * 10 changes in 300 seconds. Saving...
    Jan 26 08:07:46 16:M 26 Jan 2022 07:07:46.055 * Background saving started by pid 3924
    Jan 26 08:07:46 3924:C 26 Jan 2022 07:07:46.316 * DB saved on disk
    Jan 26 08:07:46 3924:C 26 Jan 2022 07:07:46.318 * RDB: 0 MB of memory used by copy-on-write
    Jan 26 08:07:46 16:M 26 Jan 2022 07:07:46.357 * Background saving terminated with success
    Jan 26 08:12:47 16:M 26 Jan 2022 07:12:47.001 * 10 changes in 300 seconds. Saving...
    Jan 26 08:12:47 16:M 26 Jan 2022 07:12:47.003 * Background saving started by pid 3925
    Jan 26 08:12:47 3925:C 26 Jan 2022 07:12:47.223 * DB saved on disk
    Jan 26 08:12:47 3925:C 26 Jan 2022 07:12:47.224 * RDB: 0 MB of memory used by copy-on-write
    Jan 26 08:12:47 16:M 26 Jan 2022 07:12:47.304 * Background saving terminated with success
    Jan 26 08:17:48 16:M 26 Jan 2022 07:17:48.028 * 10 changes in 300 seconds. Saving...
    Jan 26 08:17:48 16:M 26 Jan 2022 07:17:48.030 * Background saving started by pid 3926
    Jan 26 08:17:48 3926:C 26 Jan 2022 07:17:48.265 * DB saved on disk
    Jan 26 08:17:48 3926:C 26 Jan 2022 07:17:48.267 * RDB: 0 MB of memory used by copy-on-write
    Jan 26 08:17:48 16:M 26 Jan 2022 07:17:48.330 * Background saving terminated with success
    Jan 26 08:22:49 16:M 26 Jan 2022 07:22:49.045 * 10 changes in 300 seconds. Saving...
    Jan 26 08:22:49 16:M 26 Jan 2022 07:22:49.047 * Background saving started by pid 3927
    Jan 26 08:22:49 3927:C 26 Jan 2022 07:22:49.304 * DB saved on disk
    Jan 26 08:22:49 3927:C 26 Jan 2022 07:22:49.306 * RDB: 0 MB of memory used by copy-on-write
    Jan 26 08:22:49 16:M 26 Jan 2022 07:22:49.350 * Background saving terminated with success
    Jan 26 08:27:50 16:M 26 Jan 2022 07:27:50.030 * 10 changes in 300 seconds. Saving...
    Jan 26 08:27:50 16:M 26 Jan 2022 07:27:50.035 * Background saving started by pid 3928
    Jan 26 08:27:50 3928:C 26 Jan 2022 07:27:50.298 * DB saved on disk
    Jan 26 08:27:50 3928:C 26 Jan 2022 07:27:50.300 * RDB: 0 MB of memory used by copy-on-write
    Jan 26 08:27:50 16:M 26 Jan 2022 07:27:50.335 * Background saving terminated with success
    Jan 26 08:30:09 2022-01-26 07:30:09,532 WARN received SIGTERM indicating exit request
    Jan 26 08:30:09 2022-01-26 07:30:09,590 INFO waiting for redis, redis-service to die
    Jan 26 08:30:09 2022-01-26 07:30:09,603 INFO stopped: redis-service (terminated by SIGTERM)
    Jan 26 08:30:09 16:signal-handler (1643182209) Received SIGTERM scheduling shutdown...
    Jan 26 08:30:09 16:M 26 Jan 2022 07:30:09.697 # User requested shutdown...
    Jan 26 08:30:09 16:M 26 Jan 2022 07:30:09.697 * Saving the final RDB snapshot before exiting.
    Jan 26 08:30:09 16:M 26 Jan 2022 07:30:09.933 * DB saved on disk
    Jan 26 08:30:09 16:M 26 Jan 2022 07:30:09.933 * Removing the pid file.
    Jan 26 08:30:09 16:M 26 Jan 2022 07:30:09.933 # Redis is now ready to exit, bye bye...
    Jan 26 08:30:09 2022-01-26 07:30:09,952 INFO stopped: redis (exit status 0)
    

    I'm back trying this because my CODE installation was not connecting to anything other than md files, and I could not find any options, like with OnlyOffice, to assign file types to CODE. This is getting frustrating!

    A life lived in fear is a life half-lived

    nebulonN 1 Reply Last reply
    0
  • nebulonN Offline
    nebulonN Offline
    nebulon Staff
    replied to scooke on last edited by
    #9

    @scooke generally both CODE and OnlyOffice do not store anything persistently on the app itself. So given that you tried installing a fresh OnlyOffice instance altogether (uninstall+install) this issue might be more likely to be Nextcloud and their OnlyOffice connector related. So maybe look there for more info.

    1 Reply Last reply
    0
  • timconsidineT Offline
    timconsidineT Offline
    timconsidine App Dev
    replied to scooke on last edited by timconsidine
    #10

    @scooke I am now having an issue with my Onlyoffice app

    Not responding
    Fails to update
    Logs show this every few minutes

    Oct 21 17:30:59 => Initialize database
    Oct 21 17:30:59 psql: error: connection to server at "postgresql" (fd00:c107:d509::80), port 5432 failed: Connection refused
    Oct 21 17:30:59 Is the server running on that host and accepting TCP/IP connections?
    Oct 21 17:30:59 connection to server at "postgresql" (172.18.0.34), port 5432 failed: Connection refused
    Oct 21 17:30:59 Is the server running on that host and accepting TCP/IP connections?
    

    Any thoughts ?

    EDIT : I checked Services and saw Redis for this app had stopped. Restarted w/o problem.
    But postgresql is shown in orange status and is trying to restart constantly.
    Those logs show :

    Oct 21 17:38:05 Debug mode. Sleeping
    Oct 21 17:38:20 Detected existing installation
    Oct 21 17:38:20 Resetting root password
    Oct 21 17:39:21 Detected existing installation
    Oct 21 17:39:21 Resetting root password
    Oct 21 17:40:23 Detected existing installation
    Oct 21 17:40:23 Resetting root password
    

    EDIT(2) : rebooted box, postgresql restarted, seems to have cleared the issue.

    1 Reply Last reply
    2
  • nebulonN nebulon has marked this topic as solved on

  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Login

  • Don't have an account? Register

  • Login or register to search.