Skip to main content

Announcement: Downtime git.friendi.ca / wiki.friendi.ca / files.friendi.ca / drone.friendi.ca
There might be a planned downtime tomorrow 14:00 CET. I am still figuring out if it is necessary to swap the NVME storage drive of the server and am in contact with the hosting company.

Please prepare for about 4-6 hours downtime to allow raid resync.

It might be much shorter, but I feel more comfortable with that prognosis.

Also if you know your way around NVME replacement and raid resync I am open for suggestions on how to do this, maybe it is possible to resync the system while it is running, last time I did not manage to do this and had to use a rescue live #Linux system to recover.

Details on the time scheduled in your timezone:
https://www.timeanddate.com/worldclock/fixedtime.html?p1=37&iso=20211107T14&msg=Downtime%20friendica.utzer.de%20/%20git.friendi.ca%20/%20wiki.friendi.ca%20/%20files.friendi.ca%20/%20drone.friendi.ca&ah=6

#Announcement #Downtime #Friendica #Admin @Friendica Developers
#friendica #linux #admin #announcement #downtime @Friendica Developers
utzer (on squeet.me)
utzer (on squeet.me)  
•
a bit to early... need to shutdown now.
utzer (on squeet.me)
utzer (on squeet.me)  
•
could someone check for function, I need to fiddle with the RAID and the new drive, need to start the resync.
utzer (on squeet.me)
utzer (on squeet.me)  
•
@Tobias hmm yes, seems to be some gitea problem.
@Tobias
utzer (on squeet.me)
utzer (on squeet.me)  
•
@Tobias and before that it was my fault... now wiki works, but git does not.
@Tobias
utzer [Friendica]
utzer [Friendica]  
•
@Tobias
Nov 07 13:45:57 git systemd[1]: gitea.service: Main process exited, code=exited, status=226/NAMESPACE
Nov 07 13:45:57 git systemd[1]: gitea.service: Failed with result 'exit-code'.
Nov 07 13:45:59 git systemd[1]: gitea.service: Scheduled restart job, restart counter is at 41.
Nov 07 13:45:59 git systemd[1]: Stopped Gitea (Git with a cup of tea).
Nov 07 13:45:59 git systemd[1]: gitea.service: Start request repeated too quickly.
Nov 07 13:45:59 git systemd[1]: gitea.service: Failed with result 'exit-code'.
Nov 07 13:45:59 git systemd[1]: Failed to start Gitea (Git with a cup of tea).
@Tobias
utzer [Friendica]
utzer [Friendica]  
•
@Tobias hmm let me check about the SSH.
@Tobias
This entry was edited (3 years ago)
utzer [Friendica]
utzer [Friendica]  
•
@Tobias this "ProtectSystem=full" instead of "ProtectSystem=strict" did not help.
@Tobias
utzer [Friendica]
utzer [Friendica]  
•
@Tobiaschown gitea:gitea /etc/gitea/app.ini solvee the permission issue to access app.ini.
@Tobias
utzer [Friendica]
utzer [Friendica]  
•
@Tobias works without systemd, so back to systemd problem.
@Tobias
utzer [Friendica]
utzer [Friendica]  
•
@Tobias
utzer [Friendica]
utzer [Friendica]  
•
@Tobias em yes, that is what I did too, started it manually... but killed it again now.
@Tobias
utzer [Friendica]
utzer [Friendica]  
•
@Tobias seems now systemctl restart gitea.service worked and gitea keeps running.
@Tobias
utzer [Friendica]
utzer [Friendica]  
•
@Tobias if there just was some realtime communication we could use. ;-)

I have no idea what the problem was, but it seems to be solved. I will continue with something else, if there is any further problem you encounter, please let me know via Matrix, XMPP or Signal if you can.
@Tobias
utzer [Friendica]
utzer [Friendica]  
•
@Tobias hmm to me? Hmm do still have my old utzer.de Matrix address, that server I had to kill, Matrix used toooo much resources.
@Tobias
utzer [Friendica]
utzer [Friendica]  
•
@Tobias yes, sorry, I am not usually abandoning services like that, but Matrix is really frustrating ressource hogging.
@Tobias
⇧