During the installation everything semes to be ok, but try to access to my local instalation I get this erro message:
We're sorry, but something went wrong.
If you are the application owner check the logs for more information.
In app-stdout.log I get this message:
Completed 500 Internal Server Error in 18ms (ActiveRecord: 4.4ms | Elasticsearch: 0.0ms)
ActionView::Template::Error (Webpacker can't find application.css in /usr/src/app/public/packs/manifest.json. Possible causes:
1. You want to set webpacker.yml value of compile to true for your environment
unless you are using the `webpack -w` or the webpack-dev-server.
2. webpack has not yet re-run to reflect updates.
3. You have misconfigured Webpacker's config/webpacker.yml file.
4. Your webpack configuration is not creating a manifest.
Your manifest contains:
{
}
):
54: Fablab.sessionTours = [];
55: </script>
56:
57: <%= stylesheet_packs_with_chunks_tag 'application', media: 'all' %>
58: <%= stylesheet_packs_with_chunks_tag 'plugins', media: 'all' %>
59: <%= stylesheet_packs_with_chunks_tag 'printer', media: 'print' %>
60: <% unless Stylesheet.theme.nil? %>
I can’t find any manifest.json or webpacker.yml. How can I solve that problem?
Hello, thank you for your response. Now I am trying to install the software in another server. In this server I get a problem too. When I run this command I get:
If I run the command:
docker-compose down && docker-compose up
I get the following message in loop. In the log files I have the same information.
fabmanager_1 | 2021-02-24 08:38:49,729 INFO success: worker entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
fabmanager_1 | 2021-02-24 08:38:49,730 INFO exited: app (terminated by SIGABRT (core dumped); not expected)
fabmanager_1 | 2021-02-24 08:38:50,351 INFO spawned: ‹ app › with pid 11
fabmanager_1 | 2021-02-24 08:38:50,511 INFO exited: worker (terminated by SIGABRT (core dumped); not expected)
fabmanager_1 | 2021-02-24 08:38:51,512 INFO success: app entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
fabmanager_1 | 2021-02-24 08:38:51,513 INFO spawned: ‹ worker › with pid 12
fabmanager_1 | 2021-02-24 08:38:52,404 INFO exited: app (terminated by SIGABRT (core dumped); not expected)
Working on a fix by rebuilding the sleede/fab-manager docker image with another version of the 2.6.6-alpine image version of Ruby (replacing 2.6.6-alpine by 2.6.7-alpine)
UPDATE : Seems to work, I’ve successfully installed Fab-manager with the modified image (with some errors and I’ve also had to edit the initial install script) but it works !
If you want @Sylvain, we can share about this solution (I also speak French btw)
Hi @binForYou,
I updated ffi in v4.7.0 guessing that fixes the issue but if you experienced the issue with a later version, I’ll be pleased to integrate your fix in Fab-manager.
Hello @binForYou it seems I’m running into the same issue you have been. Except that Ruby 2.6.7 is already in place, but I have the same instruction error during the installation script : /usr/local/bundle/gems/ffi-1.15.1/lib/ffi/library.rb:112: [BUG] Illegal instruction at 0x00007f68eb1f4904ruby 2.6.7p197 (2021-04-05 revision 67941) [x86_64-linux-musl]
I’m on a brain new fresh install and stay stuck on this issue…
According to this thead, the issue may be related to some CPU architecture details, especially when using VM. There’s a chance that a further version of sassc fixes the issues. I’ll try to update it in the upcoming version and keep you updated.