<div>Hi,</div>
<div> </div>
<div>Just wondering if anyone else has had this problem.</div>
<div> </div>
<div>Sometimes when I make some simple changes to the <em>openser.cfg</em> config file and save, then restart openser using the <em><strong>openserctl restart</strong></em> or <strong><em>stop</em></strong> and <strong><em>
start</em></strong> commands, openser refuses to come back up with an error message, usually along the lines of "openser already running?" or "openser.pid not found" or something similar. I will see if I can find the exact wording of the error messages and post them here.
</div>
<div> </div>
<div>I can then only get it running again by copying an old (working) config into the directory and renaming it to <em>openser.cfg</em> then adding the entries back again to the config and restarting the server.</div>
<div> </div>
<div>Am I stopping and starting openser to quickly or something?</div>
<div> </div>
<div>Other things I have tried include searching for running openser processes and using <em><strong>kill xx</strong></em> or <em><strong>killall openser</strong></em> to manually terminate them, but no running processes can be found, which makes me wonder why the error message keeps saying openser is already running. Also
<strong><em>ps -ef</em></strong> and other similar commands are showing no running openser instances. <strong>openserctl moni</strong> says cannot find pid or fifo (I forget which) and <strong>openserctl ps</strong> also gives some error.
</div>
<div> </div>
<div>Sometimes when this happens I notice that the <em>openser.pid</em> file still exists even though openser has stopped running.</div>
<div> </div>
<div>Now I am wondering if it is something to do with the way openser parses the script, or whether it's to do with the ssh program I use to remotely connect to the openser server somehow not writing the file correctly when it saves. In case it's relevant, I use WinSCP ver
3.8.2 to edit my configs.</div>
<div> </div>
<div>Any ideas?</div>
<div> </div>