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


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
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
Brand Logo

Cloudron Forum
Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. DocuSeal
  3. Docuseal wouldn't crashed and wouldn't start

Docuseal wouldn't crashed and wouldn't start

Scheduled Pinned Locked Moved Solved DocuSeal
7 Posts 3 Posters 731 Views 3 Watching
  • 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.
  • avatar1024A Offline
    avatar1024A Offline
    avatar1024
    wrote on last edited by avatar1024
    #1

    Hello,

    This morning I uploaded a doc and the app crashed, I go the Cloudron page: This app is unresponsive". I tried to restart the app but it got Stuck on the "Starting" state. Then rebooted the server and same thing.

    See the log that has the error in case there is a bug:

    
2023-11-12T08:43:21.000Z ==> changing permissions
2023-11-12T08:43:21.000Z ==> starting docuseal
2023-11-12T08:43:23.000Z ==> changing permissions
2023-11-12T08:43:23.000Z ==> starting docuseal
2023-11-12T08:43:23.000Z => Booting Puma
2023-11-12T08:43:23.000Z => Rails 7.0.7 application starting in production
2023-11-12T08:43:23.000Z => Run `bin/rails server --help` for more startup options
2023-11-12T08:43:23.000Z A server is already running. Check /app/code/tmp/pids/server.pid.
2023-11-12T08:43:23.000Z Exiting
2023-11-12T08:43:24.000Z => Booting Puma
2023-11-12T08:43:24.000Z => Rails 7.0.7 application starting in production
2023-11-12T08:43:24.000Z => Run `bin/rails server --help` for more startup options
2023-11-12T08:43:24.000Z A server is already running. Check /app/code/tmp/pids/server.pid.
2023-11-12T08:43:24.000Z Exiting
2023-11-12T08:43:25.000Z ==> changing permissions
2023-11-12T08:43:25.000Z ==> starting docuseal
2023-11-12T08:43:26.000Z => Booting Puma
2023-11-12T08:43:26.000Z => Rails 7.0.7 application starting in production
2023-11-12T08:43:26.000Z => Run `bin/rails server --help` for more startup options
2023-11-12T08:43:26.000Z A server is already running. Check /app/code/tmp/pids/server.pid.
2023-11-12T08:43:26.000Z Exiting
2023-11-12T08:43:27.000Z ==> changing permissions
2023-11-12T08:43:27.000Z ==> starting docuseal
2023-11-12T08:43:28.000Z => Booting Puma
2023-11-12T08:43:28.000Z => Rails 7.0.7 application starting in production
2023-11-12T08:43:28.000Z => Run `bin/rails server --help` for more startup options
2023-11-12T08:43:28.000Z A server is already running. Check /app/code/tmp/pids/server.pid.
2023-11-12T08:43:28.000Z Exiting
2023-11-12T08:43:30.000Z ==> changing permissions
2023-11-12T08:43:30.000Z ==> starting docuseal
2023-11-12T08:43:31.000Z => Booting Puma
2023-11-12T08:43:31.000Z => Healtheck error: Error: connect ECONNREFUSED 172.18.16.128:3000
2023-11-12T08:43:31.000Z => Rails 7.0.7 application starting in production
2023-11-12T08:43:31.000Z => Run `bin/rails server --help` for more startup options
2023-11-12T08:43:31.000Z A server is already running. Check /app/code/tmp/pids/server.pid.
2023-11-12T08:43:31.000Z Exiting
2023-11-12T08:43:35.000Z ==> changing permissions
2023-11-12T08:43:35.000Z ==> starting docuseal
2023-11-12T08:43:36.000Z => Booting Puma
2023-11-12T08:43:36.000Z => Rails 7.0.7 application starting in production
2023-11-12T08:43:36.000Z => Run `bin/rails server --help` for more startup options
2023-11-12T08:43:36.000Z A server is already running. Check /app/code/tmp/pids/server.pid.
2023-11-12T08:43:36.000Z Exiting
2023-11-12T08:43:43.000Z ==> changing permissions
2023-11-12T08:43:43.000Z ==> starting docuseal
2023-11-12T08:43:44.000Z => Booting Puma
2023-11-12T08:43:44.000Z => Rails 7.0.7 application starting in production
2023-11-12T08:43:44.000Z => Run `bin/rails server --help` for more startup options
2023-11-12T08:43:44.000Z A server is already running. Check /app/code/tmp/pids/server.pid.
2023-11-12T08:43:44.000Z Exiting
2023-11-12T08:43:47.000Z => Healtheck error: Error: Timeout of 7000ms exceeded
2023-11-12T08:43:57.000Z ==> changing permissions
2023-11-12T08:43:57.000Z ==> starting docuseal
2023-11-12T08:43:57.000Z => Healtheck error: Error: Timeout of 7000ms exceeded
2023-11-12T08:43:58.000Z => Booting Puma
2023-11-12T08:43:58.000Z => Rails 7.0.7 application starting in production
2023-11-12T08:43:58.000Z => Run `bin/rails server --help` for more startup options
2023-11-12T08:43:58.000Z A server is already running. Check /app/code/tmp/pids/server.pid.
2023-11-12T08:43:58.000Z Exiting
2023-11-12T08:44:01.000Z ==> changing permissions
2023-11-12T08:44:01.000Z ==> starting docuseal
2023-11-12T08:44:01.166Z box:taskworker Starting task 14329. Logs are at /home/yellowtent/platformdata/logs/d99d4145-455f-4681-97ce-5aad9341b430/apptask.log
2023-11-12T08:44:01.182Z box:apptask run: startTask installationState: pending_restart runState: running
2023-11-12T08:44:01.182Z box:tasks update 14329: {"percent":10,"message":"Starting app services"}
2023-11-12T08:44:01.185Z box:tasks update 14329: {"percent":20,"message":"Restarting container"}
2023-11-12T08:44:01.678Z box:tasks update 14329: {"percent":80,"message":"Configuring reverse proxy"}
2023-11-12T08:44:01.706Z box:reverseproxy providerMatchesSync: subject=CN = sign.catalystcollective.org domain=sign.catalystcollective.org issuer=C = US, O = Let's Encrypt, CN = R3 wildcard=false/false prod=true/true issuerMismatch=false wildcardMismatch=false match=true
2023-11-12T08:44:01.718Z box:reverseproxy ensureCertificate: sign.catalystcollective.org acme cert exists and is up to date
2023-11-12T08:44:01.718Z box:reverseproxy expiryDate: subject=CN = sign.catalystcollective.org notBefore=Oct 30 09:57:45 2023 GMT notAfter=Jan 28 09:57:44 2024 GMT daysLeft=77.05118383101852
2023-11-12T08:44:01.718Z box:reverseproxy needsRenewal: false. force: false
2023-11-12T08:44:01.738Z box:reverseproxy writeAppLocationNginxConfig: writing config for "sign.catalystcollective.org" to /home/yellowtent/platformdata/nginx/applications/d99d4145-455f-4681-97ce-5aad9341b430/sign.catalystcollective.org.conf with options {"sourceDir":"/home/yellowtent/box","vhost":"sign.catalystcollective.org","hasIPv6":true,"ip":"172.18.16.128","port":3000,"endpoint":"app","redirectTo":null,"certFilePath":"/home/yellowtent/platformdata/nginx/cert/sign.catalystcollective.org.cert","keyFilePath":"/home/yellowtent/platformdata/nginx/cert/sign.catalystcollective.org.key","robotsTxtQuoted":null,"cspQuoted":null,"hideHeaders":[],"proxyAuth":{"enabled":false,"id":"d99d4145-455f-4681-97ce-5aad9341b430","location":"/"},"upstreamUri":"","ocsp":true,"hstsPreload":false}
2023-11-12T08:44:01.739Z box:shell reload spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/restartservice.sh nginx
2023-11-12T08:44:01.855Z box:tasks update 14329: {"percent":100,"message":"Done"}
2023-11-12T08:44:01.863Z box:tasks setCompleted - 14329: {"result":null,"error":null}
2023-11-12T08:44:01.863Z box:tasks update 14329: {"percent":100,"result":null,"error":null}
2023-11-12T08:44:01.863Z box:taskworker Task took 0.734 seconds
2023-11-12T08:44:02.000Z => Booting Puma
2023-11-12T08:44:02.000Z => Rails 7.0.7 application starting in production
2023-11-12T08:44:02.000Z => Run `bin/rails server --help` for more startup options
2023-11-12T08:44:02.000Z A server is already running. Check /app/code/tmp/pids/server.pid.
2023-11-12T08:44:02.000Z Exiting
2023-11-12T08:44:03.000Z ==> changing permissions
2023-11-12T08:44:03.000Z ==> starting docuseal
2023-11-12T08:44:04.000Z => Booting Puma
2023-11-12T08:44:04.000Z => Rails 7.0.7 application starting in production
2023-11-12T08:44:04.000Z => Run `bin/rails server --help` for more startup options
2023-11-12T08:44:04.000Z A server is already running. Check /app/code/tmp/pids/server.pid.
2023-11-12T08:44:04.000Z Exiting
2023-11-12T08:44:05.000Z ==> changing permissions
2023-11-12T08:44:05.000Z ==> starting docuseal
2023-11-12T08:44:05.000Z => Booting Puma
2023-11-12T08:44:05.000Z => Rails 7.0.7 application starting in production
2023-11-12T08:44:05.000Z => Run `bin/rails server --help` for more startup options
2023-11-12T08:44:05.000Z A server is already running. Check /app/code/tmp/pids/server.pid.
2023-11-12T08:44:05.000Z Exiting
2023-11-12T08:44:06.000Z ==> changing permissions
2023-11-12T08:44:06.000Z ==> starting docuseal
2023-11-12T08:44:07.000Z => Booting Puma
2023-11-12T08:44:07.000Z => Healtheck error: Error: Timeout of 7000ms exceeded
2023-11-12T08:44:07.000Z => Rails 7.0.7 application starting in production
2023-11-12T08:44:07.000Z => Run `bin/rails server --help` for more startup options
2023-11-12T08:44:07.000Z A server is already running. Check /app/code/tmp/pids/server.pid.
2023-11-12T08:44:07.000Z Exiting
2023-11-12T08:44:09.000Z ==> changing permissions
2023-11-12T08:44:09.000Z ==> starting docuseal
2023-11-12T08:44:10.000Z => Booting Puma
2023-11-12T08:44:10.000Z => Healtheck error: Error: connect ECONNREFUSED 172.18.16.128:3000
2023-11-12T08:44:10.000Z => Rails 7.0.7 application starting in production
2023-11-12T08:44:10.000Z => Run `bin/rails server --help` for more startup options
2023-11-12T08:44:10.000Z A server is already running. Check /app/code/tmp/pids/server.pid.
2023-11-12T08:44:10.000Z Exiting
2023-11-12T08:44:12.000Z ==> changing permissions
2023-11-12T08:44:12.000Z ==> starting docuseal
2023-11-12T08:44:13.000Z => Booting Puma
2023-11-12T08:44:13.000Z => Rails 7.0.7 application starting in production
2023-11-12T08:44:13.000Z => Run `bin/rails server --help` for more startup options
2023-11-12T08:44:13.000Z A server is already running. Check /app/code/tmp/pids/server.pid.
2023-11-12T08:44:13.000Z Exiting
2023-11-12T08:44:16.000Z ==> changing permissions
2023-11-12T08:44:16.000Z ==> starting docuseal
2023-11-12T08:44:17.000Z => Booting Puma
2023-11-12T08:44:17.000Z => Rails 7.0.7 application starting in production
2023-11-12T08:44:17.000Z => Run `bin/rails server --help` for more startup options
2023-11-12T08:44:17.000Z A server is already running. Check /app/code/tmp/pids/server.pid.
2023-11-12T08:44:17.000Z Exiting
2023-11-12T08:44:24.000Z ==> changing permissions
2023-11-12T08:44:24.000Z ==> starting docuseal
2023-11-12T08:44:25.000Z => Booting Puma
2023-11-12T08:44:25.000Z => Rails 7.0.7 application starting in production
2023-11-12T08:44:25.000Z => Run `bin/rails server --help` for more startup options
2023-11-12T08:44:25.000Z A server is already running. Check /app/code/tmp/pids/server.pid.
2023-11-12T08:44:25.000Z Exiting
2023-11-12T08:44:27.000Z => Healtheck error: Error: Timeout of 7000ms exceeded
2023-11-12T08:44:37.000Z => Healtheck error: Error: Timeout of 7000ms exceeded
2023-11-12T08:44:38.000Z ==> changing permissions
2023-11-12T08:44:38.000Z ==> starting docuseal
2023-11-12T08:44:39.000Z => Booting Puma
2023-11-12T08:44:39.000Z => Rails 7.0.7 application starting in production
2023-11-12T08:44:39.000Z => Run `bin/rails server --help` for more startup options
2023-11-12T08:44:39.000Z A server is already running. Check /app/code/tmp/pids/server.pid.
2023-11-12T08:44:39.000Z Exiting
2023-11-12T08:44:43.000Z => Healtheck error: Error: connect EHOSTUNREACH 172.18.16.128:3000
2023-11-12T08:44:53.000Z => Healtheck error: Error: connect EHOSTUNREACH 172.18.16.128:3000
2023-11-12T08:45:03.000Z => Healtheck error: Error: connect EHOSTUNREACH 172.18.16.128:3000
2023-11-12T08:45:05.000Z ==> changing permissions
2023-11-12T08:45:05.000Z ==> starting docuseal
2023-11-12T08:45:06.000Z => Booting Puma
2023-11-12T08:45:06.000Z => Rails 7.0.7 application starting in production
2023-11-12T08:45:06.000Z => Run `bin/rails server --help` for more startup options
2023-11-12T08:45:06.000Z A server is already running. Check /app/code/tmp/pids/server.pid.
2023-11-12T08:45:06.000Z Exiting
2023-11-12T08:45:13.000Z => Healtheck error: Error: connect EHOSTUNREACH 172.18.16.128:3000
2023-11-12T08:45:23.000Z => Healtheck error: Error: connect EHOSTUNREACH 172.18.16.128:3000
2023-11-12T08:45:33.000Z => Healtheck error: Error: connect EHOSTUNREACH 172.18.16.128:3000
2023-11-12T08:45:43.000Z => Healtheck error: Error: connect EHOSTUNREACH 172.18.16.128:3000
2023-11-12T08:45:53.000Z => Healtheck error: Error: connect EHOSTUNREACH 172.18.16.128:3000
2023-11-12T08:45:58.000Z ==> changing permissions
2023-11-12T08:45:58.000Z ==> starting docuseal
2023-11-12T08:45:59.000Z => Booting Puma
2023-11-12T08:45:59.000Z => Rails 7.0.7 application starting in production
2023-11-12T08:45:59.000Z => Run `bin/rails server --help` for more startup options
2023-11-12T08:45:59.000Z A server is already running. Check /app/code/tmp/pids/server.pid.
2023-11-12T08:45:59.000Z Exiting
2023-11-12T08:46:03.000Z => Healtheck error: Error: connect EHOSTUNREACH 172.18.16.128:3000
2023-11-12T08:46:13.000Z => Healtheck error: Error: connect EHOSTUNREACH 172.18.16.128:3000
2023-11-12T08:46:23.000Z => Healtheck error: Error: connect EHOSTUNREACH 172.18.16.128:3000
2023-11-12T08:46:33.000Z => Healtheck error: Error: connect EHOSTUNREACH 172.18.16.128:3000
2023-11-12T08:46:43.000Z => Healtheck error: Error: connect EHOSTUNREACH 172.18.16.128:3000
2023-11-12T08:46:53.000Z => Healtheck error: Error: connect EHOSTUNREACH 172.18.16.128:3000
2023-11-12T08:46:59.000Z ==> changing permissions
2023-11-12T08:46:59.000Z ==> starting docuseal
2023-11-12T08:47:00.000Z => Booting Puma
2023-11-12T08:47:00.000Z => Healtheck error: Error: connect ECONNREFUSED 172.18.16.128:3000
2023-11-12T08:47:00.000Z => Rails 7.0.7 application starting in production
2023-11-12T08:47:00.000Z => Run `bin/rails server --help` for more startup options
2023-11-12T08:47:00.000Z A server is already running. Check /app/code/tmp/pids/server.pid.
2023-11-12T08:47:00.000Z Exiting
2023-11-12T08:47:17.000Z => Healtheck error: Error: Timeout of 7000ms exceeded
2023-11-12T08:47:27.000Z => Healtheck error: Error: Timeout of 7000ms exceeded
2023-11-12T08:48:07.000Z ==> changing permissions
2023-11-12T08:48:07.000Z ==> starting docuseal
2023-11-12T08:48:16.000Z => Booting Puma
2023-11-12T08:48:16.000Z => Rails 7.0.7 application starting in production
2023-11-12T08:48:16.000Z => Run `bin/rails server --help` for more startup options
2023-11-12T08:48:16.000Z A server is already running. Check /app/code/tmp/pids/server.pid.
2023-11-12T08:48:16.000Z Exiting
2023-11-12T08:48:18.000Z ==> changing permissions
2023-11-12T08:48:18.000Z ==> starting docuseal
2023-11-12T08:48:19.000Z => Booting Puma
2023-11-12T08:48:19.000Z => Rails 7.0.7 application starting in production
2023-11-12T08:48:19.000Z => Run `bin/rails server --help` for more startup options
2023-11-12T08:48:19.000Z A server is already running. Check /app/code/tmp/pids/server.pid.
2023-11-12T08:48:19.000Z Exiting
2023-11-12T08:48:21.000Z ==> changing permissions
2023-11-12T08:48:21.000Z ==> starting docuseal
2023-11-12T08:48:23.000Z => Booting Puma
2023-11-12T08:48:23.000Z => Rails 7.0.7 application starting in production
2023-11-12T08:48:23.000Z => Run `bin/rails server --help` for more startup options
2023-11-12T08:48:23.000Z A server is already running. Check /app/code/tmp/pids/server.pid.
2023-11-12T08:48:23.000Z Exiting
2023-11-12T08:48:26.000Z ==> changing permissions
2023-11-12T08:48:26.000Z ==> starting docuseal
2023-11-12T08:48:27.000Z => Booting Puma
2023-11-12T08:48:27.000Z => Rails 7.0.7 application starting in production
2023-11-12T08:48:27.000Z => Run `bin/rails server --help` for more startup options
2023-11-12T08:48:27.000Z A server is already running. Check /app/code/tmp/pids/server.pid.
2023-11-12T08:48:27.000Z Exiting
2023-11-12T08:48:29.000Z ==> changing permissions
2023-11-12T08:48:30.000Z ==> starting docuseal
2023-11-12T08:48:31.000Z => Booting Puma
2023-11-12T08:48:31.000Z => Rails 7.0.7 application starting in production
2023-11-12T08:48:31.000Z => Run `bin/rails server --help` for more startup options
2023-11-12T08:48:31.000Z A server is already running. Check /app/code/tmp/pids/server.pid.
2023-11-12T08:48:31.000Z Exiting
2023-11-12T08:48:34.000Z ==> changing permissions
2023-11-12T08:48:34.000Z ==> starting docuseal
2023-11-12T08:48:36.000Z => Booting Puma
2023-11-12T08:48:36.000Z => Rails 7.0.7 application starting in production
2023-11-12T08:48:36.000Z => Run `bin/rails server --help` for more startup options
2023-11-12T08:48:36.000Z A server is already running. Check /app/code/tmp/pids/server.pid.
2023-11-12T08:48:36.000Z Exiting
2023-11-12T08:48:40.000Z ==> changing permissions
2023-11-12T08:48:40.000Z ==> starting docuseal
2023-11-12T08:48:40.000Z => Healtheck error: Error: connect ECONNREFUSED 172.18.16.128:3000
2023-11-12T08:48:42.000Z => Booting Puma
2023-11-12T08:48:42.000Z => Rails 7.0.7 application starting in production
2023-11-12T08:48:42.000Z => Run `bin/rails server --help` for more startup options
2023-11-12T08:48:42.000Z A server is already running. Check /app/code/tmp/pids/server.pid.
2023-11-12T08:48:42.000Z Exiting
2023-11-12T08:48:49.000Z ==> changing permissions
2023-11-12T08:48:49.000Z ==> starting docuseal
2023-11-12T08:48:50.000Z => Booting Puma
2023-11-12T08:48:50.000Z => Healtheck error: Error: connect ECONNREFUSED 172.18.16.128:3000
2023-11-12T08:48:50.000Z => Rails 7.0.7 application starting in production
2023-11-12T08:48:50.000Z => Run `bin/rails server --help` for more startup options
2023-11-12T08:48:50.000Z A server is already running. Check /app/code/tmp/pids/server.pid.
2023-11-12T08:48:50.000Z Exiting
2023-11-12T08:49:03.000Z ==> changing permissions
2023-11-12T08:49:03.000Z ==> starting docuseal
2023-11-12T08:49:04.000Z => Booting Puma
2023-11-12T08:49:04.000Z => Rails 7.0.7 application starting in production
2023-11-12T08:49:04.000Z => Run `bin/rails server --help` for more startup options
2023-11-12T08:49:04.000Z A server is already running. Check /app/code/tmp/pids/server.pid.
2023-11-12T08:49:04.000Z Exiting
2023-11-12T08:49:07.000Z => Healtheck error: Error: Timeout of 7000ms exceeded
2023-11-12T08:49:13.000Z => Healtheck error: Error: connect EHOSTUNREACH 172.18.16.128:3000
2023-11-12T08:49:23.000Z => Healtheck error: Error: connect EHOSTUNREACH 172.18.16.128:3000
2023-11-12T08:49:31.000Z ==> changing permissions
2023-11-12T08:49:31.000Z ==> starting docuseal
2023-11-12T08:49:31.000Z => Booting Puma
2023-11-12T08:49:31.000Z => Healtheck error: Error: connect ECONNREFUSED 172.18.16.128:3000
2023-11-12T08:49:31.000Z => Rails 7.0.7 application starting in production
2023-11-12T08:49:31.000Z => Run `bin/rails server --help` for more startup options
2023-11-12T08:49:31.000Z A server is already running. Check /app/code/tmp/pids/server.pid.
2023-11-12T08:49:31.000Z Exiting
2023-11-12T08:49:47.000Z => Healtheck error: Error: Timeout of 7000ms exceeded
2023-11-12T08:49:57.000Z => Healtheck error: Error: Timeout of 7000ms exceeded
2023-11-12T08:50:03.000Z => Healtheck error: Error: connect EHOSTUNREACH 172.18.16.128:3000
2023-11-12T08:50:13.000Z => Healtheck error: Error: connect EHOSTUNREACH 172.18.16.128:3000
2023-11-12T08:50:23.000Z ==> changing permissions
2023-11-12T08:50:23.000Z ==> starting docuseal
2023-11-12T08:50:23.000Z => Healtheck error: Error: connect EHOSTUNREACH 172.18.16.128:3000
2023-11-12T08:50:24.000Z => Booting Puma
2023-11-12T08:50:24.000Z => Rails 7.0.7 application starting in production
2023-11-12T08:50:24.000Z => Run `bin/rails server --help` for more startup options
2023-11-12T08:50:24.000Z A server is already running. Check /app/code/tmp/pids/server.pid.
2023-11-12T08:50:24.000Z Exiting
2023-11-12T08:50:37.000Z => Healtheck error: Error: Timeout of 7000ms exceeded
2023-11-12T08:50:47.000Z => Healtheck error: Error: Timeout of 7000ms exceeded

    I tried to restore from backup (from last night) but that also failed and then realised that for some reason my backup storage got unmounted. I remounted it, then backup worked fine and the app is now running fine.

    Still not sure what caused the error in the first place. All now works fine but thought it might be useful to report this incident happened since this app package is "unstable state".

    1 Reply Last reply
    2
    • D Offline
      D Offline
      docuseal
      wrote on last edited by
      #2

      @avatar1024 this issue has been fixed in the latest version:
      https://github.com/docusealco/docuseal/commit/7b15111e8f2f202f5fffdbcf445517dd92d1e533

      avatar1024A 1 Reply Last reply
      5
      • D docuseal

        @avatar1024 this issue has been fixed in the latest version:
        https://github.com/docusealco/docuseal/commit/7b15111e8f2f202f5fffdbcf445517dd92d1e533

        avatar1024A Offline
        avatar1024A Offline
        avatar1024
        wrote on last edited by avatar1024
        #3

        @docuseal Thank you! But do you mean in 1.2.7? If so I was already running that one.

        girishG 1 Reply Last reply
        0
        • avatar1024A avatar1024

          @docuseal Thank you! But do you mean in 1.2.7? If so I was already running that one.

          girishG Offline
          girishG Offline
          girish
          Staff
          wrote on last edited by
          #4

          @avatar1024 Can you try this?

          • Put app in repair mode
          • Using Web terminal, delete /tmp/docuseal/tmp/pids/server.pid
          • Disable repair mode

          Does this make the app work ?

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

            Well, I pushed a new package now that cleans up the tmp on restart . Can you update and check?

            1 Reply Last reply
            0
            • avatar1024A Offline
              avatar1024A Offline
              avatar1024
              wrote on last edited by
              #6

              @girish , thanks for this. As explained in my first message, I mainly posted to let you know that happened for info / debug / to improve the package. I myself restored from a previous backup and the app is running fine so I cannot test / reproduce it (unfortunately / fortunately 😆 ).

              1 Reply Last reply
              1
              • girishG Offline
                girishG Offline
                girish
                Staff
                wrote on last edited by
                #7

                @avatar1024 ah, I missed that part that you restored! Thanks for reporting.

                1 Reply Last reply
                0
                • nebulonN nebulon marked this topic as a question on
                • nebulonN nebulon has marked this topic as solved on
                Reply
                • Reply as topic
                Log in to reply
                • Oldest to Newest
                • Newest to Oldest
                • Most Votes

                • Login
                • Don't have an account? Register
                • Login or register to search.
                • First post
                  Last post
                0
                • Categories
                • Recent
                • Tags
                • Popular
                • Bookmarks
                • Search