ruby - Rails-Thin server stopped on Production(live) mode.Website down -
I have placed my rubber production on the rail project. I was running thin on the production mode. Now suddenly the thin server seems to stop and try to start the following error: -
/home/webuser/.rvm/gems/ruby -1.9.3-p545@woa/gems/thin-1.6.2/lib/thin/daemonizing.rb:158:in 'Delete': Read-Only File System - / tmp / pids / thin.3000.pid /home/webuser/.rvm/gems/ruby-global-family-index.html from Errno :: EROFS), / home / webuser / 158: / home / webuser / /gems/thin-1.6.2/lib/thin/daemonizing.rb:175:IN/home/webuser/.rvm/gems/ruby in 'remove_pid_file' from .rvm / gems / ruby-1.9.3-p545 @ woa In 'remove_stale_pid_file' from -1.9.3-p545@woa/gems/thin-1.6 2 / lib / thin / daemonizing.rb: 43: From /home/webuser/.rvm/gems/ruby-1.9.3-p545@woa/gems/thin-1.6.2/lib/thin/controllers in `Demois' /controller.rb:62:IN/home/webuser/.rvm/gems/ruby-1.9.3-p545@woa/gems/thin-1.6.2/lib/thin/run `Start 'Ner.rb: 199 : Run `run_common 'from /home/webuser/.rvm/gems/ruby-1.9.3-p545@woa/gems/thin-1.6.2/lib/thin/runner.rb:155:in! '/home/webuser/.rvm/gems/ruby-1.9.3-p545@woa/gems/thin-1.6.2/bin/thin:6:in' at the top (required) & gt; From 'load' to /home/webuser/.rvm/gems/ruby-1.9.3-p545@woa/bin/thin:23:in/home/webuser/.rvm/gems/ruby-1.9.3-p545@ Woa / bin / thin: 23: `& lt; Main & gt; From `/home/webuser/.rvm/gems/ruby-1.9.3-p545@woa/bin/ruby_executable_hooks15: From '/home/webuser/.rvm/gems/ruby-1.9.3-p545@' aval 'woa / Bin / ruby_executable_hooks: 15: in `& lt; Main & gt; '
I tried to remove the pid by using $ lsof -wni tcp: 3000
. But no output is available for this. FileZilla also went through and tried to temporarily remove PM, but the following error is happening. General failure (server must provide error description)
.
Now my website is one hour
The immediate error is that your program old file Can not be removed. In each process that runs on your computer, it has a number; Servers often save this number in a file, to stop the two running simultaneously
You get the error message, though - "read-only file system" - Seldom is a good sign If your computer has to face hard drive problems, then this file system can only remotely read to prevent further damage. Production of dmesg
can give you an idea of whether this matter is here. You can probably back up your server and reboot it and run it, but you should be looking for impending hard drive failure.
Comments
Post a Comment