I've installed Odoo/OpnnERP, and I've put the openerp-server daemon in /etc/init.d to get it started automatically on Ubuntu startup. It gets started normally on every reboot and works fine. But sometimes it goes down automatically, I don't know any pattern when it goes down, and I also can't see any reason in the log file (/var/log/openerp/openerp-server.log). It just goes down without any logs. When I find it down, I have to reboot manually to get it started again.
Any help on spotting the issue which causes openerp-server to stop automatically without any logs?
Thanks,
Abdul
I have Odoo under a DO droplet and all I did was upgrading the droplet, that's it!
Just found an answer to the above issue. Here is the solution
Related
I'm trying to disable the IIS localhost from Windows, without success. The only thing I'm finding is, that you have to disable the IIS option that's found in the Windows-Features. I disabled it and restarted my computer multiple times, but each time the localhost is still the default IIS...
Is there anything else I can do? I'm a complete newbie on this topic, so please tell me if there's information missing in my question.
Also tried the advice in this article, without success. The terminal does say, that the service has stopped, but localhost is still the Windows IIS. https://www.names.co.uk/support/1607-how_do_i_stop_iis_via_command_prompt_.html
Seems clearing the browser cache solved the problem.
Am using Plotly's Dash and trying to run the sample app code which they have provided here: https://plot.ly/dash/getting-started#dash-app-layout
Am having trouble with the ports. The code on being run shows this in the console:
However , even after making changes to the code, the output in the web app shows no change.
Basically, when I'm implementing a different code: the web app continues to display the output from the previous run!
The CTRL+C doesn't seem to help and doesn't really quit or cause any change to the application. Please let me know what shall help.
I ran the new code using a new port(8049) and that worked but doesn't solve the initial basic issue!
I've had the same issues, and find that a full restart of the app is necessary to get some changes to propagate in the app after a file update.
In POSIX, you could run sudo killall python or similar. Looks like you're running Windows, so taskmanager or taskkill /F /IM python.exe.
The [1]: Looks like a Jupyter kernel is running? If so, try restarting the kernel.
For me CTRL+C doesn't work either, but CTRL+Pause/Break button stops execution.
One day, out of nothing, my app decided not to die.
After pressing ctrl + c when I inspect port it's still there and not only on my machine but also on server that is managed by PM2 so I need to go there each time and kill the process by hand. I tried to look for issues in my code and when I couldn't I just though that it's simply one of the dependencies fault and soon there will be a fix. It was slightly annoying but I could kill the process with kill -9 PID and I had most of the tasks I had on front-end side so it wasn't that big issue. Today, more than a week later problem it's still here.
I went back in history, picked a commit that I made weeks ago, where everything worked perfectly fine, switched NodeJS from 5.1.0 to 4.2.1, cleared npm cache, reinstalled all dependencies and I still see the problem.
I'm using LoopbackJS, but normally I start the app simply with "node server/server.js" and then the problem described above happens, but if I use "slc run" and then try to kill the app with ctrl + c it just hangs forever, I mean I can press ctrl+c as many times as I want and it's still running in console foreground.
If instead of pressing ctrl+c I kill the tab in console, app dies without problems.
This is what I see after running "lsof -i tcp:4000" when the app is supposed to be dead but is not
Edit:
Running and killing it with Strongloop process manager - slc start/slc stop works fine but it would be more convenient to use normal way of running NodeJS app (node server.js) during development and it doesn't change the fact that there is some issue and it would be better to not hide it under the carpet.
Out of anger I stripped out my app to the most basic elements. File by file, piece by piece and I found the answer.
The culprit was phantomJS - https://github.com/sgentle/phantomjs-node. PATCH version 0.8.2 introduced this bug. Fix was created almost a month ago, merged a week ago but not published on npm yet.
I have a service that needs to complete before I can let Linux start up continue. I'd rather not have to specify each service and target in a Before= statement in my .service files. In SysVInit, I just specified the start number I wanted with chkconfig.
I have tried defining a foo.target and a foo.service and set it with require= and after= for network.target (I need networking) as well as before=multi-user.target. This doesn't seem to be working. I have set up the foo.target.wants directory to have a symlink to foo.service.
I have tried turning on debug in system.conf, to see what's wrong and had disastrous results.
Any help would be appreciated.
I finally got everything working the way I wanted. It's not pretty, but...
I changed the systemd default to a special target that wants what services are needed and runs my script at the end. At the end of my script, systemctl isolate multi-user is issued. I've verified that this works as desired.
Annoyingly, when developing in MSVC2010, my EXE will not link (ie cannot emit output file) because the application experience service in Windows 7 has stopped.
I've no idea how these two things can be related, but i've been "fixing" it my manually restarting the process in the Windows service manager. Then i can link. At a random time later it will happen again. the process is set to automatic by default.
i've had enough of this madness. does anyone have any ideas? thanks.
Please try this: http://gauravpandey.com/wordpress/?p=291 it should work. it has atleast worked for me though I have not really understood the relationship between the two issues.