pawelmalak / flame

Flame is self-hosted startpage for your server. Easily manage your apps and bookmarks with built-in editors.
MIT License
5.33k stars 264 forks source link

[BUG] Flame is never able to load applications and bookmarks #345

Open JaneJeon opened 2 years ago

JaneJeon commented 2 years ago

Deployment details:


Bug description:

It hangs indefinitely, trying to load applications and bookmarks.

Screen Shot 2022-04-19 at 4 54 06 AM

Steps to reproduce:

Just visiting the homepage you can see the error, but this error actually started occurring after I restored from backup. All of the JSON files and SQLite databases seem to be fine, but somehow Flame is unable to read whatever files it's trying to read, as you can see from the logs:

Screen Shot 2022-04-19 at 4 54 19 AM

I've tried everything obvious, no cigar. It's throwing a bunch of ENOENT errors in a loop, but the logs don't even show which files it's trying to read (and failing).

For debugging purposes, here is the filesystem structure within /app/data:

├── assets
│   ├── config.json
│   ├── customQueries.json
│   ├── db_backups
│   │   └── db-201-backup.sqlite
│   ├── db.sqlite
│   └── uploads
├── config.json
├── customQueries.json
├── db_backups
│   ├── db-201-backup.sqlite
│   ├── db-210-backup.sqlite
│   ├── db-211-backup.sqlite
│   ├── db-220-backup.sqlite
│   ├── db-221-backup.sqlite
│   ├── db-222-backup.sqlite
│   └── db-230-backup.sqlite
├── db.sqlite
├── flame.css
├── themes.json
└── uploads

And ls -l of the /app directory:

-rwxr-xr-x    1 root     root         12392 Mar 25 13:54 CHANGELOG.md
-rwxr-xr-x    1 root     root          1088 Mar 21 10:48 LICENSE.md
-rwxr-xr-x    1 root     root          7477 Mar 24 14:07 README.md
-rwxr-xr-x    1 root     root           560 Mar 21 10:48 Socket.js
-rwxr-xr-x    1 root     root           357 Mar 21 10:48 Sockets.js
-rwxr-xr-x    1 root     root           977 Mar 23 12:24 api.js
drwxr-xr-x   10 root     root          4096 Mar 25 13:33 controllers
drwxr-xr-x    5 node     node          4096 Apr 18 07:30 data
drwxr-xr-x    4 root     root          4096 Mar 21 10:51 db
drwxr-xr-x    2 root     root          4096 Mar 25 13:33 middleware
drwxr-xr-x    2 root     root          4096 Mar 21 10:51 models
drwxr-xr-x  284 root     root         12288 Mar 21 11:08 node_modules
-rwxr-xr-x    1 root     root        303955 Mar 23 11:24 package-lock.json
-rwxr-xr-x    1 root     root          1279 Mar 21 10:48 package.json
drwxr-xr-x    4 root     root          4096 Mar 25 13:56 public
drwxr-xr-x    2 root     root          4096 Mar 25 13:33 routes
-rwxr-xr-x    1 root     root          1025 Mar 21 10:48 server.js
drwxr-xr-x    3 root     root          4096 Mar 25 13:33 utils
JaneJeon commented 2 years ago

The issue was ""resolved"" after hours (without any action from me), but it is the most curious thing and in either case we need better error messages for this kind of stuff.

Screen Shot 2022-04-19 at 9 29 17 AM