-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debian daemon not works #1671
Comments
I don't for your version. But I see that the init script has been changed between 0.6.1 and 0.6.13. I do the update from one to the other and I keep the old script. No problem for me. Maybe try with the old one. Update : The one that works for me is with the commit number : 98c719c |
I've seen this today. If I run I think there's something wrong with the startup procedure. |
http://download.prodigy7.de/files/programs/any/syncthing/syncthing This might help. |
Thanks your feedback! But you have to dump the log info here so we can help you... |
Right now I'm using the init script just before 98c719c and it's working fine. I'll try the latest script and see what's in the log once I get back home. |
I tried to watch log, there is empty |
@Mirkhamidov I've met someone has similar issue before, so if there is no log for daemon(whatever service tool you use), it does not start Gogs anyway. The final solution to him is switch to supervisor and works very well. |
Can you explain how? |
tnx, I will try |
😉 |
@JokerQyou it helped!))) but, now, if I restart server I got in
but if I did
it starts properly
im using postgresql, why it wrote |
This just shows that gogs is compiled with SQLite3 support, nothing else. |
I suppose it's just because SQLite is supported, it did not say 'SQLite enabled' or 'SQLite in use'. I think it might be because by the time Gogs starts, your Postgres daemon has not yet finished starting. |
@tboerger, @JokerQyou I see @JokerQyou this one 98c719c But what should I do, to work it properly? |
I know very little about shell script, so sorry I cannot say. I've not tested server reboot yet. |
@Mirkhamidov I think you should just Google the posgresql error and I can't help because the error message is not in English 😭 |
The meaaage simply indicates the database server has started On Mon, Sep 28, 2015, 19:18 无闻 notifications@github.com wrote:
|
@JokerQyou Hmm... if just a info message, when pg returns as error? |
gogs need to start after pg started |
@Mirkhamidov seems like you found solution? |
no, just, not using gogs yet. Will wait when it will be ready. |
Then what does this comment suppose to mean... ? |
I think we know the reason why it's behaving that way -- Gogs started before Postgres server is ready, but I don't have any solution. |
I'm not using init.d but for systemd, see https://github.com/gogits/gogs/blob/master/scripts/systemd/gogs.service#L5 . I suppose init.d has something similar... |
ok |
It should be easy to tell the init script that it requires postgreSQL. Those that use PostgreSQL change line: https://github.com/gogits/gogs/blob/master/scripts/init/debian/gogs#L4 to:
This will ensure that gogs runs after postgreSQL daemon has started. You need to enable the postgresql script to run on start too if it hasn't been already done.
|
After use the current init file (not the file in the release) (4a05c4a#diff-2010a922586cdf277b495c360c8a66a3) it works. |
@seeseekey thanks your confirmation! |
This change fixed the issue for me as well |
Close for now but open for continuing discussion. |
Istalled under user git to directory /home/git/gogs
If run
./gogs/gogs web --config ./gogs/custom/conf/app.ini
all works
than a file from
scripts/init/debian/gogs
were copied to/etc/init.d/gogs
and all works with adding it to system done.when
$ sudo service gogs start
server gogs not work (it gives '502 Bad Gateway')
and if
and nothing here
and here
sudo netstat -tulpn
and more
What im doing wron?
The text was updated successfully, but these errors were encountered: