GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE

  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Conversation

Notices

  1. Embed this notice
    Nozamelon (nozaki@poa.st)'s status on Tuesday, 15-Nov-2022 22:05:01 JST Nozamelon Nozamelon
    • Alex Gleason
    @alex I'm in the middle of updating my instance, and made the mistake of updating Elrang, which caused everything to crash. I found your fix on here: gitlab.com/-/snippets/2121092

    I finally didn't have any issues with the installation that I was getting before. I'm getting a new error when I checked the status of the pleroma service after finishing your guide.

    '''
    Active: failed (Result: exit-code) since Tue 2022-11-15 02:33:30 PST; 35s ago
    Process: 269338 ExecStart=/var/lib/pleroma/.asdf/shims/mix phx.server (code=exited, status=1/FAILURE)
    '''
    I had some issues with mix deps.get step, but I saw a comment further down that recommended deleting the _build directory and going through it again.

    When following your fix, I noticed that .tool-versions and pleroma.service were already updated, so I didn't make any changes to them other than confirming they were already fixed.

    I'm clueless when it comes to a lot of this stuff, so you require more information I'm happy to provide it. I've been digging around for a while online trying out different fixes, and I'm worried one of my attempts may have messed everything up. I tried a few things before I found your fix.

    Thank you.
    In conversation Tuesday, 15-Nov-2022 22:05:01 JST from poa.st permalink

    Attachments

    1. Domain not in remote thumbnail source whitelist: gitlab.com
      Pleroma: Switching to asdf ($2121092) · Snippets · Snippets · GitLab
      GitLab.com
    • Embed this notice
      Alex Gleason (alex@gleasonator.com)'s status on Tuesday, 15-Nov-2022 22:05:01 JST Alex Gleason Alex Gleason
      in reply to

      @nozaki Dang, that error says basically nothing. Maybe try journalctl -u pleroma?

      In conversation Tuesday, 15-Nov-2022 22:05:01 JST permalink
    • Embed this notice
      Alex Gleason (alex@gleasonator.com)'s status on Tuesday, 15-Nov-2022 22:12:34 JST Alex Gleason Alex Gleason
      in reply to
      @nozaki Look for errors.
      In conversation Tuesday, 15-Nov-2022 22:12:34 JST permalink
    • Embed this notice
      Nozamelon (nozaki@poa.st)'s status on Tuesday, 15-Nov-2022 22:12:35 JST Nozamelon Nozamelon
      in reply to
      • Alex Gleason

      @alex Should I just paste everything in here?

      In conversation Tuesday, 15-Nov-2022 22:12:35 JST permalink
    • Embed this notice
      Alex Gleason (alex@gleasonator.com)'s status on Tuesday, 15-Nov-2022 22:13:27 JST Alex Gleason Alex Gleason
      in reply to
      • Alex Gleason

      @nozaki And add --since "1 hour ago" to see recent logs.

      In conversation Tuesday, 15-Nov-2022 22:13:27 JST permalink
    • Embed this notice
      Alex Gleason (alex@gleasonator.com)'s status on Tuesday, 15-Nov-2022 22:19:27 JST Alex Gleason Alex Gleason
      in reply to
      @nozaki Where are you seeing the error then? What's not working? Is the pleroma service stopped?
      In conversation Tuesday, 15-Nov-2022 22:19:27 JST permalink
    • Embed this notice
      Nozamelon (nozaki@poa.st)'s status on Tuesday, 15-Nov-2022 22:19:28 JST Nozamelon Nozamelon
      in reply to
      • Alex Gleason
      @alex There's nothing the logs from 1-2 hours ago. And everything in it without any time things on it is an [info] request.
      In conversation Tuesday, 15-Nov-2022 22:19:28 JST permalink
    • Embed this notice
      Nozamelon (nozaki@poa.st)'s status on Tuesday, 15-Nov-2022 22:21:39 JST Nozamelon Nozamelon
      in reply to
      • Alex Gleason
      @alex Yeah sorry. I just restarted it.
      In conversation Tuesday, 15-Nov-2022 22:21:39 JST permalink
    • Embed this notice
      Alex Gleason (alex@gleasonator.com)'s status on Tuesday, 15-Nov-2022 22:21:39 JST Alex Gleason Alex Gleason
      in reply to
      @nozaki And that fixed it?
      In conversation Tuesday, 15-Nov-2022 22:21:39 JST permalink
    • Embed this notice
      Josh Adams (josh@social.rebased.network)'s status on Tuesday, 15-Nov-2022 23:37:55 JST Josh Adams Josh Adams
      in reply to
      • Alex Gleason
      Fwiw `ss -ntlp` will tell you what's listening for tcp traffic. Useful for finding these things
      In conversation Tuesday, 15-Nov-2022 23:37:55 JST permalink
      Alex Gleason likes this.
    • Embed this notice
      Alex Gleason (alex@gleasonator.com)'s status on Tuesday, 15-Nov-2022 23:39:04 JST Alex Gleason Alex Gleason
      in reply to
      @nozaki Weird that something would be trying to remove a dep? You should ls -alh /opt/pleroma and make sure it's all owned by pleroma:pleroma
      In conversation Tuesday, 15-Nov-2022 23:39:04 JST permalink
    • Embed this notice
      Nozamelon (nozaki@poa.st)'s status on Tuesday, 15-Nov-2022 23:39:05 JST Nozamelon Nozamelon
      in reply to
      • Alex Gleason

      @alex Sorry I have a meeting to go to right now, I will get back to you in two hours. I appreciate your patience Alex. I will return soon. ‘’’ ** (File.Error) could not remove files and directories recursively from “/opt/pleroma/_build/prod/lib/captcha”: permission denied mix[273119]: (elixir 1.11.4) lib/file.ex:1291: File.rm_rf!/1 mix[273119]: (mix 1.11.4) lib/mix/tasks/deps.compile.ex:81: anonymous fn/4 in Mix.Tasks.Deps.Compile.compile/2 mix[273119]: (elixir 1.11.4) lib/enum.ex:1411: Enum.”-map/2-lists^map/1-0-“/2 mix[273119]: (mix 1.11.4) lib/mix/tasks/deps.compile.ex:79: Mix.Tasks.Deps.Compile.compile/2 mix[273119]: (mix 1.11.4) lib/mix/tasks/deps.loadpaths.ex:89: Mix.Tasks.Deps.Loadpaths.deps_check/2 mix[273119]: (mix 1.11.4) lib/mix/tasks/deps.loadpaths.ex:28: Mix.Tasks.Deps.Loadpaths.run/1 mix[273119]: (mix 1.11.4) lib/mix/task.ex:394: anonymous fn/3 in Mix.Task.run_task/3 mix[273119]: (mix 1.11.4) lib/mix/task.ex:437: Mix.Task.get_task_or_run/3 systemd[1]: pleroma.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: pleroma.service: Failed with result ‘exit-code’. ‘’’

      Thank you.

      In conversation Tuesday, 15-Nov-2022 23:39:05 JST permalink
    • Embed this notice
      Nozamelon (nozaki@poa.st)'s status on Wednesday, 16-Nov-2022 00:49:46 JST Nozamelon Nozamelon
      in reply to
      • Alex Gleason
      @alex Thank you Alex for your patience with someone who can't even use markdown properly.

      There are some that are owned by root. I'll change everything to pleroma and report back.
      In conversation Wednesday, 16-Nov-2022 00:49:46 JST permalink
      Alex Gleason likes this.
    • Embed this notice
      Nozamelon (nozaki@poa.st)'s status on Wednesday, 16-Nov-2022 02:49:42 JST Nozamelon Nozamelon
      in reply to
      • Alex Gleason
      @alex Thank you for your patience, I everything has changed ownership to pleroma now, and I got a new error that is telling me I need to recompile some BEAM files with a 23 compiler.

      This is where I go back to your original fix right? Do I need to run these commands again?

      mix local.hex --force
      mix local.rebar --force
      mix deps.get
      MIX_ENV=prod mix compile
      In conversation Wednesday, 16-Nov-2022 02:49:42 JST permalink
    • Embed this notice
      Alex Gleason (alex@gleasonator.com)'s status on Wednesday, 16-Nov-2022 02:49:42 JST Alex Gleason Alex Gleason
      in reply to

      @nozaki Run asdf current to ensure Elixir is being managed by asdf. But yeah, looks right.

      In conversation Wednesday, 16-Nov-2022 02:49:42 JST permalink
    • Embed this notice
      Alex Gleason (alex@gleasonator.com)'s status on Wednesday, 16-Nov-2022 03:52:39 JST Alex Gleason Alex Gleason
      in reply to
      @nozaki Yes, you should nuke _build and recompile. I'm not entirely sure what happened, but it looks like maybe two different versions of Erlang were used.
      In conversation Wednesday, 16-Nov-2022 03:52:39 JST permalink
    • Embed this notice
      Nozamelon (nozaki@poa.st)'s status on Wednesday, 16-Nov-2022 03:52:40 JST Nozamelon Nozamelon
      in reply to
      • Alex Gleason
      @alex Giving this a shot. Thank you Alex.
      In conversation Wednesday, 16-Nov-2022 03:52:40 JST permalink
    • Embed this notice
      Nozamelon (nozaki@poa.st)'s status on Wednesday, 16-Nov-2022 03:52:40 JST Nozamelon Nozamelon
      in reply to
      • Alex Gleason
      @alex Getting compilation issues again.

      09:57:40.061 [error] beam/beam_load.c(1879): Error loading module prometheus_htt p:
      This BEAM file was compiled for a later version of the run-time system than 23 .
      To fix this, please recompile this module with an 23 compiler.
      (Use of opcode 178; this emulator supports only up to 170.)

      In the comments of your code snippets, someone recommends deleting the _build directory and then trying it again. Should I try that?
      In conversation Wednesday, 16-Nov-2022 03:52:40 JST permalink
    • Embed this notice
      Nozamelon (nozaki@poa.st)'s status on Wednesday, 16-Nov-2022 03:54:46 JST Nozamelon Nozamelon
      in reply to
      • Alex Gleason
      @alex Thank you Alex, doing this now. And I guess I will update soapbox while I'm at it.
      In conversation Wednesday, 16-Nov-2022 03:54:46 JST permalink
      Alex Gleason likes this.
    • Embed this notice
      Nozamelon (nozaki@poa.st)'s status on Wednesday, 16-Nov-2022 04:15:53 JST Nozamelon Nozamelon
      in reply to
      • Alex Gleason
      @alex Got this error, did I not set up some of the fixes correctly?

      ** (Mix) Could not compile dependency :parse_trans, "/var/lib/pleroma/.asdf/installs/elixir/1.11/.mix/rebar3 bare compile --paths="/opt/pleroma/_build/prod/lib/*/ebin"" command failed. You can recompile this dependency with "mix deps.compile parse_trans", update it with "mix deps.update parse_trans" or clean it with "mix deps.clean parse_trans"
      In conversation Wednesday, 16-Nov-2022 04:15:53 JST permalink
    • Embed this notice
      Alex Gleason (alex@gleasonator.com)'s status on Wednesday, 16-Nov-2022 04:15:53 JST Alex Gleason Alex Gleason
      in reply to
      @nozaki Try simply running the compile command again
      In conversation Wednesday, 16-Nov-2022 04:15:53 JST permalink
    • Embed this notice
      Alex Gleason (alex@gleasonator.com)'s status on Wednesday, 16-Nov-2022 04:18:13 JST Alex Gleason Alex Gleason
      in reply to
      @nozaki I'm a bit wary your .tool-versions says Elixir 1.11.

      https://gitlab.com/soapbox-pub/rebased/-/blob/develop/.tool-versions
      In conversation Wednesday, 16-Nov-2022 04:18:13 JST permalink

      Attachments

      1. Domain not in remote thumbnail source whitelist: gitlab.com
        .tool-versions · develop · Soapbox / Rebased · GitLab
        Fediverse backend written in Elixir. The recommended backend for Soapbox. https://soapbox.pub
    • Embed this notice
      Nozamelon (nozaki@poa.st)'s status on Wednesday, 16-Nov-2022 04:18:14 JST Nozamelon Nozamelon
      in reply to
      • Alex Gleason
      @alex Thank you for your help. I got the same error.
      In conversation Wednesday, 16-Nov-2022 04:18:14 JST permalink
    • Embed this notice
      Nozamelon (nozaki@poa.st)'s status on Wednesday, 16-Nov-2022 04:33:21 JST Nozamelon Nozamelon
      in reply to
      • Alex Gleason
      @alex Sorry, I was following the steps in the fix I found from a year ago. My .tool-versions says:

      elixir 1.11
      erlang 23.3.4

      Should I change it to what you have in your link?
      In conversation Wednesday, 16-Nov-2022 04:33:21 JST permalink
    • Embed this notice
      Alex Gleason (alex@gleasonator.com)'s status on Wednesday, 16-Nov-2022 04:33:21 JST Alex Gleason Alex Gleason
      in reply to

      @nozaki Yeah, I’d give that a try. You’d have to run asdf install then re-run the setup commands.

      In conversation Wednesday, 16-Nov-2022 04:33:21 JST permalink
    • Embed this notice
      Nozamelon (nozaki@poa.st)'s status on Wednesday, 16-Nov-2022 07:43:13 JST Nozamelon Nozamelon
      in reply to
      • Alex Gleason

      @alex Hi Alex, again thank you for your help. I confirmed via ‘asdf current’ that I am running the right version of erlang and elixir. I nuked the _build directory, and started to compile again and got some errors again.

      ===> Compiling _build/default/plugins/rebar3_archive_plugin/src/rebar3_archive_plugin.erl failed _build/default/plugins/aleppo/ebin/rebar3_archive_plugin.bea#:none: error writing file: permission denied

      _build/default/plugins/rebar3_archive_plugin/src/rebar3_archive_plugin.erl:27:1: Warning: missing specification for function do/1

      * (Mix) Could not compile dependency :accept, “/var/lib/pleroma/.asdf/installs/elixir/1.13/.mix/rebar3 bare compile –paths /opt/pleroma/_build/prod/lib//ebin” command failed. Errors may have been logged above. You can recompile this dependency with “mix deps.compile accept”, update it with “mix deps.update accept” or clean it with “mix deps.clean accept”

      Is this a permissions issue? I confirmed that pleroma owns everything in the /opt/pleroma directory.

      Thank you again for your assistance.

      In conversation Wednesday, 16-Nov-2022 07:43:13 JST permalink
    • Embed this notice
      Nozamelon (nozaki@poa.st)'s status on Wednesday, 16-Nov-2022 07:43:13 JST Nozamelon Nozamelon
      in reply to
      • Alex Gleason
      @alex Thank you for your help today, but I must go to bed now as I am in euro time. If you have any further ideas please let me know and I will take a crack at them in the morning.
      In conversation Wednesday, 16-Nov-2022 07:43:13 JST permalink
      Alex Gleason likes this.

Feeds

  • Activity Streams
  • RSS 2.0
  • Atom
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.