Post 2340392 by ij@nerdculture.de
 (DIR) More posts by ij@nerdculture.de
 (DIR) Post #2264128 by ij@nerdculture.de
       2018-12-20T21:13:59Z
       
       0 likes, 1 repeats
       
       I'm thinking about moving the #Mastodon installation on https://nerdculture.de/ from a dedicated VM with 1x vCPU and 3 GB RAM to my webserver VM with 4x vCPUs and 16 GB RAM (the same as my Friendica node on https://nerdica.net/)?Moving Mastodon user dir and IP address is the simple part of that idea, but I'm unsure about the rest of the required software stack incl. certbot not interfering with dehydrated... Hmmm....
       
 (DIR) Post #2264160 by SetecAstronomy@hackers.town
       2018-12-25T03:11:11Z
       
       0 likes, 0 repeats
       
       @ij I don't have the details, but you're going to want to make sure the database(s) get copied over too (unless that server isn't moving)
       
 (DIR) Post #2276324 by ij@nerdculture.de
       2018-12-25T13:44:28Z
       
       0 likes, 0 repeats
       
       @SetecAstronomy - Database is already on a different (database) host and will be the same. :-)
       
 (DIR) Post #2338028 by hankg@mastodon.technology
       2018-12-25T03:18:58Z
       
       0 likes, 0 repeats
       
       @ij keep us posted !
       
 (DIR) Post #2338029 by ij@nerdculture.de
       2018-12-27T15:26:03Z
       
       0 likes, 0 repeats
       
       @hankg @SetecAstronomy - Today I've migrated my Mastodon instance to another VM. Lesson learned from that: when the filesystem for ~/live is mounted with mount option "user" you can't execute anything on that filesystem. Another issue was that on that existing VM systemd-shim was installed, which played not well with systemd files. And then streaming service is not running, because something is still broken: https://silverhaze.org/s/bLWBJZkYsrHZbM4
       
 (DIR) Post #2338030 by SetecAstronomy@hackers.town
       2018-12-27T15:28:22Z
       
       0 likes, 0 repeats
       
       @ij @hankg Now that's interesting. That's the same issue I was having with glitchsoc, I just assumed I had broken something while fiddling with stuff but now it makes me wonder. I never did get it resolved.
       
 (DIR) Post #2339150 by ij@nerdculture.de
       2018-12-27T16:12:53Z
       
       0 likes, 0 repeats
       
       @SetecAstronomy @hankg - no good news... all other tips like npm rebuild uws or so didn't help so far. Maybe @Gargron has an idea... Here again the error log: https://silverhaze.org/s/bLWBJZkYsrHZbM4
       
 (DIR) Post #2340392 by ij@nerdculture.de
       2018-12-27T17:03:54Z
       
       0 likes, 0 repeats
       
       @SetecAstronomy @hankg @Gargron - ok, apparently there is an issue with uws at the moment (or forever ;)). Anyway I think I fixed my issue by restoring live/node_modules from last nights backup. Something that is of course not possible when following the install instruction on github. But at least my streaming service seems to be up again: # netstat -tulpen | grep 4000tcp        0      0 0.0.0.0:4000            0.0.0.0:*               LISTEN      1002       434059     2993/node
       
 (DIR) Post #2340393 by SetecAstronomy@hackers.town
       2018-12-27T17:07:39Z
       
       0 likes, 0 repeats
       
       @ij @hankg @Gargron Excellent. I have one install that's not presenting that symptom, so I should be able to do something similar. Thanks for following up!