Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

APP_DEBUG is set to true while APP_ENV is not local #389

Open
krishnakanthpps opened this issue Jul 28, 2022 · 21 comments
Open

APP_DEBUG is set to true while APP_ENV is not local #389

krishnakanthpps opened this issue Jul 28, 2022 · 21 comments

Comments

@krishnakanthpps
Copy link

krishnakanthpps commented Jul 28, 2022

I used the docker installation on Amazon Linux EC2 instance.

While trying to login with a new user I am getting this error.

Initially it says there was an issue and please reload. When I do a refresh of the page while trying access /dashboard URL I get this error.

APP_DEBUG is set to true while APP_ENV is not local

This could make your application vulnerable to remote execution. Read more about Ignition security.

ErrorException
Trying to access array offset on value of type null (View: /usr/socioboard/app/socioboard-web-php/Modules/Home/Resources/views/UserDashboard.blade.php)

Routing
Controller
Modules\Home\Http\Controllers\DashboardController@index
Route name
dashboard
Route parameters

Middleware
web
authenticateUser
checkPlanExpiry

@vaughngx4
Copy link
Contributor

APP_DEBUG is set to true while APP_ENV is not local is expected, if you would like to disable debug use docker exec -it socioboard bash and edit ./socioboard-web-php/.env using vi(!! THIS DISABLES THE LOG FILE BELOW !!).

When you get the error telling you to refresh the page, you should check logs using `docker exec -it socioboard bash -c "cat /usr/socioboard/app/socioboard-web-php/storage/logs/laravel.log" to see what the error was.

@krishnakanthpps
Copy link
Author

Logs seems to be empty.

bash-5.1# ls
app framework logs
bash-5.1# cd logs
bash-5.1# ls
bash-5.1# pwd
/usr/socioboard/app/socioboard-web-php/storage/logs
bash-5.1# ls -a
. .. .gitignore
bash-5.1#

@vaughngx4
Copy link
Contributor

What about the pm2 logs?

@krishnakanthpps
Copy link
Author

krishnakanthpps commented Jul 28, 2022

bash-5.1# cat pm2.log
2022-07-28T10:33:10: PM2 log: ===============================================================================
2022-07-28T10:33:10: PM2 log: --- New PM2 Daemon started ----------------------------------------------------
2022-07-28T10:33:10: PM2 log: Time : Thu Jul 28 2022 10:33:10 GMT+0000 (Coordinated Universal Time)
2022-07-28T10:33:10: PM2 log: PM2 version : 5.2.0
2022-07-28T10:33:10: PM2 log: Node.js version : 16.16.0
2022-07-28T10:33:10: PM2 log: Current arch : x64
2022-07-28T10:33:10: PM2 log: PM2 home : /root/.pm2
2022-07-28T10:33:10: PM2 log: PM2 PID file : /root/.pm2/pm2.pid
2022-07-28T10:33:10: PM2 log: RPC socket file : /root/.pm2/rpc.sock
2022-07-28T10:33:10: PM2 log: BUS socket file : /root/.pm2/pub.sock
2022-07-28T10:33:10: PM2 log: Application log path : /root/.pm2/logs
2022-07-28T10:33:10: PM2 log: Worker Interval : 30000
2022-07-28T10:33:10: PM2 log: Process dump file : /root/.pm2/dump.pm2
2022-07-28T10:33:10: PM2 log: Concurrent actions : 2
2022-07-28T10:33:10: PM2 log: SIGTERM timeout : 1600
2022-07-28T10:33:10: PM2 log: ===============================================================================
bash-5.1# cd logs
bash-5.1# ls
bash-5.1#
bash-5.1#
bash-5.1# pwd
/root/.pm2/logs
bash-5.1#

@vaughngx4
Copy link
Contributor

vaughngx4 commented Jul 28, 2022

docker exec -it socioboard su-exec node pm2 logs

@krishnakanthpps
Copy link
Author

yep. same.

[root@ip-172-31-1-42 Socioboard-5.0]# docker exec -it socioboard su-exec node pm2 logs

                    -------------

/\\\\\\_/\\/\\/\\\\_
_/\/////////\_/\\\
/\\\/\///////\_
/\_
/\_/\//\_/\//\_/////\_
_/\\\\\\/
/\\///\/\/
/\_
/\/
/\/////////
/\_
///\/
/\_/\//_____
/\_
/\_////\_____/\//_____
/\_/\_/\_/\/__________
/\_/\_/\_/\\\\\\\_
_////////////////////////

                      Runtime Edition

    PM2 is a Production Process Manager for Node.js applications
                 with a built-in Load Balancer.

            Start and Daemonize any application:
            $ pm2 start app.js

            Load Balance 4 instances of api.js:
            $ pm2 start api.js -i 4

            Monitor in production:
            $ pm2 monitor

            Make pm2 auto-boot at server restart:
            $ pm2 startup

            To go further checkout:
            http://pm2.io/


                    -------------

[PM2] Spawning PM2 daemon with pm2_home=/home/node/.pm2
[PM2] PM2 Successfully daemonized
[TAILING] Tailing last 15 lines for [all] processes (change the value with --lines option)
/home/node/.pm2/pm2.log last 15 lines:
PM2 | 2022-07-28T10:40:01: PM2 log: --- New PM2 Daemon started ----------------------------------------------------
PM2 | 2022-07-28T10:40:01: PM2 log: Time : Thu Jul 28 2022 10:40:01 GMT+0000 (Coordinated Universal Time)
PM2 | 2022-07-28T10:40:01: PM2 log: PM2 version : 5.2.0
PM2 | 2022-07-28T10:40:01: PM2 log: Node.js version : 16.16.0
PM2 | 2022-07-28T10:40:01: PM2 log: Current arch : x64
PM2 | 2022-07-28T10:40:01: PM2 log: PM2 home : /home/node/.pm2
PM2 | 2022-07-28T10:40:01: PM2 log: PM2 PID file : /home/node/.pm2/pm2.pid
PM2 | 2022-07-28T10:40:01: PM2 log: RPC socket file : /home/node/.pm2/rpc.sock
PM2 | 2022-07-28T10:40:01: PM2 log: BUS socket file : /home/node/.pm2/pub.sock
PM2 | 2022-07-28T10:40:01: PM2 log: Application log path : /home/node/.pm2/logs
PM2 | 2022-07-28T10:40:01: PM2 log: Worker Interval : 30000
PM2 | 2022-07-28T10:40:01: PM2 log: Process dump file : /home/node/.pm2/dump.pm2
PM2 | 2022-07-28T10:40:01: PM2 log: Concurrent actions : 2
PM2 | 2022-07-28T10:40:01: PM2 log: SIGTERM timeout : 1600
PM2 | 2022-07-28T10:40:01: PM2 log: ===============================================================================

@vaughngx4
Copy link
Contributor

That's not right, there are meant to be services running. Keep in mind you can't make too many changes once the container has been created. It was designed to set everything on first run. If you need to make changes, kill the containers(databases are stored in volumes so login etc. won't be affected) and redeploy. See Docker.README.md on uninstalling.

@krishnakanthpps
Copy link
Author

Sure. At one of the places I saw an error stating that sequelize did not run. I will try to see if that error comes again and will share in this thread.

@krishnakanthpps
Copy link
Author

bash-5.1# ls -lrt
total 36
-rw-r--r-- 1 socioboa socioboa 0 Jul 28 11:50 publish.server-out.log
-rw-r--r-- 1 socioboa socioboa 0 Jul 28 11:50 feeds.server-error.log
-rw-r--r-- 1 socioboa socioboa 0 Jul 28 11:50 notify.server-error.log
-rw-r--r-- 1 socioboa socioboa 0 Jul 28 11:50 update.server-error.log
-rw-r--r-- 1 socioboa socioboa 5218 Jul 28 11:50 publish.server-error.log
-rw-r--r-- 1 socioboa socioboa 133 Jul 28 11:50 notify.server-out.log
-rw-r--r-- 1 socioboa socioboa 131 Jul 28 11:50 admin.server-out.log
-rw-r--r-- 1 socioboa socioboa 336 Jul 28 11:50 admin.server-error.log
-rw-r--r-- 1 socioboa socioboa 133 Jul 28 11:50 update.server-out.log
-rw-r--r-- 1 socioboa socioboa 133 Jul 28 11:50 feeds.server-out.log
-rw-r--r-- 1 socioboa socioboa 298 Jul 28 11:54 user.server-out.log
-rw-r--r-- 1 socioboa socioboa 2457 Jul 28 11:54 user.server-error.log
bash-5.1# cat user.server-error.log
TypeError: Cannot read properties of null (reading 'account_count')
at default (file:///usr/socioboard/app/socioboard-api/User/middleware/authentication.middleware.js:31:71)
at Layer.handle [as handle_request] (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/layer.js:95:5)
at trim_prefix (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:328:13)
at /usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:286:9
at Function.process_params (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:346:12)
at next (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:280:10)
at /usr/socioboard/app/socioboard-api/User/node_modules/express/lib/application.js:240:9
at /usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:646:15
at next (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:265:14)
at expressInit (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/middleware/init.js:40:5)
at Layer.handle [as handle_request] (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/layer.js:95:5)
at trim_prefix (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:328:13)
at /usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:286:9
at Function.process_params (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:346:12)
at next (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:280:10)
at query (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/middleware/query.js:45:5)
at Layer.handle [as handle_request] (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/layer.js:95:5)
at trim_prefix (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:328:13)
at /usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:286:9
at Function.process_params (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:346:12)
at next (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:280:10)
at Function.handle (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:175:3)

@krishnakanthpps
Copy link
Author

A complete error for pm2 logs

[root@ip-172-31-1-42 Socioboard-5.0]# docker exec -it socioboard su-exec socioboard pm2 logs
[TAILING] Tailing last 15 lines for [all] processes (change the value with --lines option)
/home/socioboard/.pm2/pm2.log last 15 lines:
PM2 | 2022-07-28T11:50:42: PM2 log: Concurrent actions : 2
PM2 | 2022-07-28T11:50:42: PM2 log: SIGTERM timeout : 1600
PM2 | 2022-07-28T11:50:42: PM2 log: ===============================================================================
PM2 | 2022-07-28T11:50:42: PM2 log: App [user.server:0] starting in -fork mode-
PM2 | 2022-07-28T11:50:42: PM2 log: App [user.server:0] online
PM2 | 2022-07-28T11:50:43: PM2 log: App [feeds.server:1] starting in -fork mode-
PM2 | 2022-07-28T11:50:43: PM2 log: App [feeds.server:1] online
PM2 | 2022-07-28T11:50:43: PM2 log: App [publish.server:2] starting in -fork mode-
PM2 | 2022-07-28T11:50:43: PM2 log: App [publish.server:2] online
PM2 | 2022-07-28T11:50:44: PM2 log: App [notify.server:3] starting in -fork mode-
PM2 | 2022-07-28T11:50:44: PM2 log: App [notify.server:3] online
PM2 | 2022-07-28T11:50:45: PM2 log: App [update.server:4] starting in -fork mode-
PM2 | 2022-07-28T11:50:45: PM2 log: App [update.server:4] online
PM2 | 2022-07-28T11:50:46: PM2 log: App [admin.server:5] starting in -fork mode-
PM2 | 2022-07-28T11:50:46: PM2 log: App [admin.server:5] online

/home/socioboard/.pm2/logs/feeds.server-error.log last 15 lines:
/home/socioboard/.pm2/logs/publish.server-out.log last 15 lines:
/home/socioboard/.pm2/logs/notify.server-error.log last 15 lines:
/home/socioboard/.pm2/logs/update.server-error.log last 15 lines:
/home/socioboard/.pm2/logs/notify.server-out.log last 15 lines:
3|notify.s | Mysql database connected
3|notify.s | Mongo Database has been connected.
3|notify.s | service listening on http://localhost:3004 with development Environment!

/home/socioboard/.pm2/logs/publish.server-error.log last 15 lines:
2|publish. | at require (node:internal/modules/cjs/helpers:102:18)
2|publish. | at Object. (/usr/socioboard/app/socioboard-api/Common/node_modules/sharp/lib/constructor.js:8:1)
2|publish. | at Module._compile (node:internal/modules/cjs/loader:1105:14)
2|publish. | at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10)
2|publish. | at Module.load (node:internal/modules/cjs/loader:981:32)
2|publish. | at Function.Module._load (node:internal/modules/cjs/loader:822:12)
2|publish. | at Module.require (node:internal/modules/cjs/loader:1005:19)
2|publish. | at Module.Hook._require.Module.require (/usr/local/lib/node_modules/pm2/node_modules/require-in-the-middle/index.js:80:39)
2|publish. | at require (node:internal/modules/cjs/helpers:102:18)
2|publish. | at Object. (/usr/socioboard/app/socioboard-api/Common/node_modules/sharp/lib/index.js:3:15)
2|publish. | at Module._compile (node:internal/modules/cjs/loader:1105:14)
2|publish. | at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10)
2|publish. | at Module.load (node:internal/modules/cjs/loader:981:32)
2|publish. | at Function.Module._load (node:internal/modules/cjs/loader:822:12)
2|publish. | at Module.require (node:internal/modules/cjs/loader:1005:19)

/home/socioboard/.pm2/logs/admin.server-error.log last 15 lines:
5|admin.se | Thu, 28 Jul 2022 11:50:55 GMT express-session deprecated undefined resave option; provide resave option at node_modules/admin-bro-expressjs/plugin.js:176:14
5|admin.se | Thu, 28 Jul 2022 11:50:55 GMT express-session deprecated undefined saveUninitialized option; provide saveUninitialized option at node_modules/admin-bro-expressjs/plugin.js:176:14

/home/socioboard/.pm2/logs/admin.server-out.log last 15 lines:
5|admin.se | Mysql database connected
5|admin.se | AdminBro: bundle ready
5|admin.se | admin panel listening on http://localhost:8080/admin with development Environment!

/home/socioboard/.pm2/logs/update.server-out.log last 15 lines:
4|update.s | Mysql database connected
4|update.s | Mongo Database has been connected.
4|update.s | service listening on http://localhost:3003 with development Environment!

/home/socioboard/.pm2/logs/feeds.server-out.log last 15 lines:
1|feeds.se | Mysql database connected
1|feeds.se | Mongo Database has been connected.
1|feeds.se | service listening on http://localhost:3001 with development Environment!

/home/socioboard/.pm2/logs/user.server-out.log last 15 lines:
0|user.ser | Mysql database connected
0|user.ser | Mongo Database has been connected.
0|user.ser | service listening on http://localhost:3000 with development Environment!
0|user.ser | POST /register 200 149.364 ms - 128
0|user.ser | POST /login 200 34.984 ms - 3856
0|user.ser | GET /v1/team/get-details 500 9.632 ms - 2877

/home/socioboard/.pm2/logs/user.server-error.log last 15 lines:
0|user.ser | at /usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:646:15
0|user.ser | at next (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:265:14)
0|user.ser | at expressInit (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/middleware/init.js:40:5)
0|user.ser | at Layer.handle [as handle_request] (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/layer.js:95:5)
0|user.ser | at trim_prefix (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:328:13)
0|user.ser | at /usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:286:9
0|user.ser | at Function.process_params (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:346:12)
0|user.ser | at next (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:280:10)
0|user.ser | at query (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/middleware/query.js:45:5)
0|user.ser | at Layer.handle [as handle_request] (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/layer.js:95:5)
0|user.ser | at trim_prefix (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:328:13)
0|user.ser | at /usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:286:9
0|user.ser | at Function.process_params (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:346:12)
0|user.ser | at next (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:280:10)
0|user.ser | at Function.handle (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:175:3)

@vaughngx4
Copy link
Contributor

I fixed a sequelize error recently, are you using my fork?

@vaughngx4
Copy link
Contributor

bash-5.1# ls -lrt total 36 -rw-r--r-- 1 socioboa socioboa 0 Jul 28 11:50 publish.server-out.log -rw-r--r-- 1 socioboa socioboa 0 Jul 28 11:50 feeds.server-error.log -rw-r--r-- 1 socioboa socioboa 0 Jul 28 11:50 notify.server-error.log -rw-r--r-- 1 socioboa socioboa 0 Jul 28 11:50 update.server-error.log -rw-r--r-- 1 socioboa socioboa 5218 Jul 28 11:50 publish.server-error.log -rw-r--r-- 1 socioboa socioboa 133 Jul 28 11:50 notify.server-out.log -rw-r--r-- 1 socioboa socioboa 131 Jul 28 11:50 admin.server-out.log -rw-r--r-- 1 socioboa socioboa 336 Jul 28 11:50 admin.server-error.log -rw-r--r-- 1 socioboa socioboa 133 Jul 28 11:50 update.server-out.log -rw-r--r-- 1 socioboa socioboa 133 Jul 28 11:50 feeds.server-out.log -rw-r--r-- 1 socioboa socioboa 298 Jul 28 11:54 user.server-out.log -rw-r--r-- 1 socioboa socioboa 2457 Jul 28 11:54 user.server-error.log bash-5.1# cat user.server-error.log TypeError: Cannot read properties of null (reading 'account_count') at default (file:///usr/socioboard/app/socioboard-api/User/middleware/authentication.middleware.js:31:71) at Layer.handle [as handle_request] (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/layer.js:95:5) at trim_prefix (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:328:13) at /usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:286:9 at Function.process_params (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:346:12) at next (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:280:10) at /usr/socioboard/app/socioboard-api/User/node_modules/express/lib/application.js:240:9 at /usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:646:15 at next (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:265:14) at expressInit (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/middleware/init.js:40:5) at Layer.handle [as handle_request] (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/layer.js:95:5) at trim_prefix (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:328:13) at /usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:286:9 at Function.process_params (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:346:12) at next (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:280:10) at query (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/middleware/query.js:45:5) at Layer.handle [as handle_request] (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/layer.js:95:5) at trim_prefix (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:328:13) at /usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:286:9 at Function.process_params (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:346:12) at next (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:280:10) at Function.handle (/usr/socioboard/app/socioboard-api/User/node_modules/express/lib/router/index.js:175:3)

Yes this makes me think it is a database error. You'd be best off deleting everything, volumes, containers and data folder. Clone my fork and start over.

@krishnakanthpps
Copy link
Author

I was picking it from the socioboard. Let me head over to your fork and try again.

@vaughngx4
Copy link
Contributor

Ah that explains it. I've pushed fixes that haven't been merged yet.

@krishnakanthpps
Copy link
Author

The error continues. this time the site doesnt even come up for some weird reason. for both 8000 and 8080 I find "This site can’t be reached" error.

[root@ip-172-31-1-42 Socioboard-5.0]# docker exec -it socioboard su-exec node pm2 logs
[TAILING] Tailing last 15 lines for [all] processes (change the value with --lines option)
/home/node/.pm2/pm2.log last 15 lines:
PM2 | 2022-07-28T15:57:30: PM2 log: Concurrent actions : 2
PM2 | 2022-07-28T15:57:30: PM2 log: SIGTERM timeout : 1600
PM2 | 2022-07-28T15:57:30: PM2 log: ===============================================================================
PM2 | 2022-07-28T15:57:30: PM2 log: App [user.server:0] starting in -fork mode-
PM2 | 2022-07-28T15:57:30: PM2 log: App [user.server:0] online
PM2 | 2022-07-28T15:57:31: PM2 log: App [feeds.server:1] starting in -fork mode-
PM2 | 2022-07-28T15:57:31: PM2 log: App [feeds.server:1] online
PM2 | 2022-07-28T15:57:31: PM2 log: App [publish.server:2] starting in -fork mode-
PM2 | 2022-07-28T15:57:31: PM2 log: App [publish.server:2] online
PM2 | 2022-07-28T15:57:32: PM2 log: App [notify.server:3] starting in -fork mode-
PM2 | 2022-07-28T15:57:32: PM2 log: App [notify.server:3] online
PM2 | 2022-07-28T15:57:33: PM2 log: App [update.server:4] starting in -fork mode-
PM2 | 2022-07-28T15:57:33: PM2 log: App [update.server:4] online
PM2 | 2022-07-28T15:57:34: PM2 log: App [admin.server:5] starting in -fork mode-
PM2 | 2022-07-28T15:57:34: PM2 log: App [admin.server:5] online

/home/node/.pm2/logs/notify.server-out.log last 15 lines:
3|notify.s | Mysql database connected

/home/node/.pm2/logs/notify.server-error.log last 15 lines:
3|notify.s | at processIncomingData (/usr/socioboard/app/socioboard-api/Common/node_modules/mongodb/lib/cmap/message_stream.js:144:12)
3|notify.s | at MessageStream._write (/usr/socioboard/app/socioboard-api/Common/node_modules/mongodb/lib/cmap/message_stream.js:42:5)
3|notify.s | at writeOrBuffer (node:internal/streams/writable:389:12)
3|notify.s | at _write (node:internal/streams/writable:330:10)
3|notify.s | at MessageStream.Writable.write (node:internal/streams/writable:334:10)
3|notify.s | at Socket.ondata (node:internal/streams/readable:754:22)
3|notify.s | at Socket.emit (node:events:527:28)
3|notify.s | at addChunk (node:internal/streams/readable:315:12)
3|notify.s | at readableAddChunk (node:internal/streams/readable:289:9)
3|notify.s | at Socket.Readable.push (node:internal/streams/readable:228:10)
3|notify.s | at TCP.onStreamRead (node:internal/stream_base_commons:190:23) {
3|notify.s | ok: 0,
3|notify.s | code: 18,
3|notify.s | codeName: 'AuthenticationFailed'
3|notify.s | }

/home/node/.pm2/logs/admin.server-error.log last 15 lines:
5|admin.se | Thu, 28 Jul 2022 15:57:42 GMT express-session deprecated undefined resave option; provide resave option at node_modules/admin-bro-expressjs/plugin.js:176:14
5|admin.se | Thu, 28 Jul 2022 15:57:42 GMT express-session deprecated undefined saveUninitialized option; provide saveUninitialized option at node_modules/admin-bro-expressjs/plugin.js:176:14

/home/node/.pm2/logs/admin.server-out.log last 15 lines:
5|admin.se | Mysql database connected
5|admin.se | AdminBro: bundle ready
5|admin.se | admin panel listening on http://socio.mydomain.example:8080/admin with development Environment!

/home/node/.pm2/logs/user.server-out.log last 15 lines:
0|user.ser | at writeOrBuffer (node:internal/streams/writable:389:12)
0|user.ser | at _write (node:internal/streams/writable:330:10)
0|user.ser | at MessageStream.Writable.write (node:internal/streams/writable:334:10)
0|user.ser | at Socket.ondata (node:internal/streams/readable:754:22)
0|user.ser | at Socket.emit (node:events:527:28)
0|user.ser | at addChunk (node:internal/streams/readable:315:12)
0|user.ser | at readableAddChunk (node:internal/streams/readable:289:9)
0|user.ser | at Socket.Readable.push (node:internal/streams/readable:228:10)
0|user.ser | at TCP.onStreamRead (node:internal/stream_base_commons:190:23) {
0|user.ser | ok: 0,
0|user.ser | code: 18,
0|user.ser | codeName: 'AuthenticationFailed'
0|user.ser | }
0|user.ser | }
0|user.ser | Unhandled Rejection: Authentication failed. Promise Promise { 'Authentication failed.' }

/home/node/.pm2/logs/user.server-error.log last 15 lines:
0|user.ser | at MessageStream._write (/usr/socioboard/app/socioboard-api/Common/node_modules/mongodb/lib/cmap/message_stream.js:42:5)
0|user.ser | at writeOrBuffer (node:internal/streams/writable:389:12)
0|user.ser | at _write (node:internal/streams/writable:330:10)
0|user.ser | at MessageStream.Writable.write (node:internal/streams/writable:334:10)
0|user.ser | at Socket.ondata (node:internal/streams/readable:754:22)
0|user.ser | at Socket.emit (node:events:527:28)
0|user.ser | at addChunk (node:internal/streams/readable:315:12)
0|user.ser | at readableAddChunk (node:internal/streams/readable:289:9)
0|user.ser | at Socket.Readable.push (node:internal/streams/readable:228:10)
0|user.ser | at TCP.onStreamRead (node:internal/stream_base_commons:190:23) {
0|user.ser | ok: 0,
0|user.ser | code: 18,
0|user.ser | codeName: 'AuthenticationFailed'
0|user.ser | }
0|user.ser | Authentication failed.

/home/node/.pm2/logs/publish.server-error.log last 15 lines:
2|publish. | at processIncomingData (/usr/socioboard/app/socioboard-api/Common/node_modules/mongodb/lib/cmap/message_stream.js:144:12)
2|publish. | at MessageStream._write (/usr/socioboard/app/socioboard-api/Common/node_modules/mongodb/lib/cmap/message_stream.js:42:5)
2|publish. | at writeOrBuffer (node:internal/streams/writable:389:12)
2|publish. | at _write (node:internal/streams/writable:330:10)
2|publish. | at MessageStream.Writable.write (node:internal/streams/writable:334:10)
2|publish. | at Socket.ondata (node:internal/streams/readable:754:22)
2|publish. | at Socket.emit (node:events:527:28)
2|publish. | at addChunk (node:internal/streams/readable:315:12)
2|publish. | at readableAddChunk (node:internal/streams/readable:289:9)
2|publish. | at Socket.Readable.push (node:internal/streams/readable:228:10)
2|publish. | at TCP.onStreamRead (node:internal/stream_base_commons:190:23) {
2|publish. | ok: 0,
2|publish. | code: 18,
2|publish. | codeName: 'AuthenticationFailed'
2|publish. | }

/home/node/.pm2/logs/publish.server-out.log last 15 lines:
2|publish. | at MessageStream._write (/usr/socioboard/app/socioboard-api/Common/node_modules/mongodb/lib/cmap/message_stream.js:42:5)
2|publish. | at writeOrBuffer (node:internal/streams/writable:389:12)
2|publish. | at _write (node:internal/streams/writable:330:10)
2|publish. | at MessageStream.Writable.write (node:internal/streams/writable:334:10)
2|publish. | at Socket.ondata (node:internal/streams/readable:754:22)
2|publish. | at Socket.emit (node:events:527:28)
2|publish. | at addChunk (node:internal/streams/readable:315:12)
2|publish. | at readableAddChunk (node:internal/streams/readable:289:9)
2|publish. | at Socket.Readable.push (node:internal/streams/readable:228:10)
2|publish. | at TCP.onStreamRead (node:internal/stream_base_commons:190:23) {
2|publish. | ok: 0,
2|publish. | code: 18,
2|publish. | codeName: 'AuthenticationFailed'
2|publish. | }
2|publish. | }

/home/node/.pm2/logs/update.server-error.log last 15 lines:
4|update.s | at processIncomingData (/usr/socioboard/app/socioboard-api/Common/node_modules/mongodb/lib/cmap/message_stream.js:144:12)
4|update.s | at MessageStream._write (/usr/socioboard/app/socioboard-api/Common/node_modules/mongodb/lib/cmap/message_stream.js:42:5)
4|update.s | at writeOrBuffer (node:internal/streams/writable:389:12)
4|update.s | at _write (node:internal/streams/writable:330:10)
4|update.s | at MessageStream.Writable.write (node:internal/streams/writable:334:10)
4|update.s | at Socket.ondata (node:internal/streams/readable:754:22)
4|update.s | at Socket.emit (node:events:527:28)
4|update.s | at addChunk (node:internal/streams/readable:315:12)
4|update.s | at readableAddChunk (node:internal/streams/readable:289:9)
4|update.s | at Socket.Readable.push (node:internal/streams/readable:228:10)
4|update.s | at TCP.onStreamRead (node:internal/stream_base_commons:190:23) {
4|update.s | ok: 0,
4|update.s | code: 18,
4|update.s | codeName: 'AuthenticationFailed'
4|update.s | }

/home/node/.pm2/logs/update.server-out.log last 15 lines:
4|update.s | at MessageStream._write (/usr/socioboard/app/socioboard-api/Common/node_modules/mongodb/lib/cmap/message_stream.js:42:5)
4|update.s | at writeOrBuffer (node:internal/streams/writable:389:12)
4|update.s | at _write (node:internal/streams/writable:330:10)
4|update.s | at MessageStream.Writable.write (node:internal/streams/writable:334:10)
4|update.s | at Socket.ondata (node:internal/streams/readable:754:22)
4|update.s | at Socket.emit (node:events:527:28)
4|update.s | at addChunk (node:internal/streams/readable:315:12)
4|update.s | at readableAddChunk (node:internal/streams/readable:289:9)
4|update.s | at Socket.Readable.push (node:internal/streams/readable:228:10)
4|update.s | at TCP.onStreamRead (node:internal/stream_base_commons:190:23) {
4|update.s | ok: 0,
4|update.s | code: 18,
4|update.s | codeName: 'AuthenticationFailed'
4|update.s | }
4|update.s | }

/home/node/.pm2/logs/feeds.server-out.log last 15 lines:
1|feeds.se | at MessageStream._write (/usr/socioboard/app/socioboard-api/Common/node_modules/mongodb/lib/cmap/message_stream.js:42:5)
1|feeds.se | at writeOrBuffer (node:internal/streams/writable:389:12)
1|feeds.se | at _write (node:internal/streams/writable:330:10)
1|feeds.se | at MessageStream.Writable.write (node:internal/streams/writable:334:10)
1|feeds.se | at Socket.ondata (node:internal/streams/readable:754:22)
1|feeds.se | at Socket.emit (node:events:527:28)
1|feeds.se | at addChunk (node:internal/streams/readable:315:12)
1|feeds.se | at readableAddChunk (node:internal/streams/readable:289:9)
1|feeds.se | at Socket.Readable.push (node:internal/streams/readable:228:10)
1|feeds.se | at TCP.onStreamRead (node:internal/stream_base_commons:190:23) {
1|feeds.se | ok: 0,
1|feeds.se | code: 18,
1|feeds.se | codeName: 'AuthenticationFailed'
1|feeds.se | }
1|feeds.se | }

/home/node/.pm2/logs/feeds.server-error.log last 15 lines:
1|feeds.se | at processIncomingData (/usr/socioboard/app/socioboard-api/Common/node_modules/mongodb/lib/cmap/message_stream.js:144:12)
1|feeds.se | at MessageStream._write (/usr/socioboard/app/socioboard-api/Common/node_modules/mongodb/lib/cmap/message_stream.js:42:5)
1|feeds.se | at writeOrBuffer (node:internal/streams/writable:389:12)
1|feeds.se | at _write (node:internal/streams/writable:330:10)
1|feeds.se | at MessageStream.Writable.write (node:internal/streams/writable:334:10)
1|feeds.se | at Socket.ondata (node:internal/streams/readable:754:22)
1|feeds.se | at Socket.emit (node:events:527:28)
1|feeds.se | at addChunk (node:internal/streams/readable:315:12)
1|feeds.se | at readableAddChunk (node:internal/streams/readable:289:9)
1|feeds.se | at Socket.Readable.push (node:internal/streams/readable:228:10)
1|feeds.se | at TCP.onStreamRead (node:internal/stream_base_commons:190:23) {
1|feeds.se | ok: 0,
1|feeds.se | code: 18,
1|feeds.se | codeName: 'AuthenticationFailed'
1|feeds.se | }

@vaughngx4
Copy link
Contributor

vaughngx4 commented Jul 28, 2022

See Docker.README.md on uninstalling. Your mongo volume may still exist from a previous attempt.

EDIT: Please read the ReadMe in full, the update changed a lot.

@krishnakanthpps
Copy link
Author

I still have not been able to get running with docker. The manual installation seems to be a huge pain.

I created a new AWS EC2 Amazon Linux instance and restarted the whole process. I am able to see the nginx home page but not able to view :8000/login or :8080/admin pages.

Any suggestion on where the logs are located to view whats going wrong? I have tried searching in /var/www/log or /var/nginx/log but they seem to be empty.

@krishnakanthpps
Copy link
Author

[PM2] Done.
┌─────┬───────────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │
├─────┼───────────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 5 │ admin.server │ default │ 1.0.0 │ fork │ 1404 │ 0s │ 0 │ online │ 0% │ 680.0kb │ node │ disabled │
│ 1 │ feeds.server │ default │ 1.0.0 │ fork │ 1332 │ 3s │ 0 │ online │ 20% │ 88.6mb │ node │ disabled │
│ 3 │ notify.server │ default │ 5.0.0 │ fork │ 1368 │ 2s │ 0 │ online │ 20% │ 61.0mb │ node │ disabled │
│ 2 │ publish.server │ default │ 1.0.0 │ fork │ 1350 │ 3s │ 0 │ online │ 20% │ 70.0mb │ node │ disabled │
│ 4 │ update.server │ default │ 1.0.0 │ fork │ 1386 │ 1s │ 0 │ online │ 40% │ 52.7mb │ node │ disabled │
│ 0 │ user.server │ default │ 1.0.0 │ fork │ 1312 │ 3s │ 0 │ online │ 40% │ 91.5mb │ node │ disabled │
└─────┴───────────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘
Starting Frontend
Application key set successfully.
Starting Laravel development server: http://0.0.0.0:8000
[Sun Jul 31 06:48:52 2022] PHP 8.0.18 Development Server (http://0.0.0.0:8000) started

/docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
/docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/
/docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh
10-listen-on-ipv6-by-default.sh: info: IPv6 listen already enabled
/docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh
20-envsubst-on-templates.sh: Running envsubst on /etc/nginx/templates/socioboard.conf.template to /etc/nginx/conf.d/socioboard.conf
/docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh
/docker-entrypoint.sh: Configuration complete; ready for start up
2022/07/31 06:48:14 [emerg] 1#1: cannot load certificate "/ssl/cert.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/ssl/cert.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)
nginx: [emerg] cannot load certificate "/ssl/cert.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/ssl/cert.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)
/docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
/docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/
/docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh
10-listen-on-ipv6-by-default.sh: info: IPv6 listen already enabled
/docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh
20-envsubst-on-templates.sh: Running envsubst on /etc/nginx/templates/socioboard.conf.template to /etc/nginx/conf.d/socioboard.conf
/docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh
/docker-entrypoint.sh: Configuration complete; ready for start up
2022/07/31 06:48:40 [notice] 1#1: using the "epoll" event method
2022/07/31 06:48:40 [notice] 1#1: nginx/1.23.1
2022/07/31 06:48:40 [notice] 1#1: built by gcc 10.2.1 20210110 (Debian 10.2.1-6)
2022/07/31 06:48:40 [notice] 1#1: OS: Linux 5.10.130-118.517.amzn2.x86_64
2022/07/31 06:48:40 [notice] 1#1: getrlimit(RLIMIT_NOFILE): 32768:65536
2022/07/31 06:48:40 [notice] 1#1: start worker processes
2022/07/31 06:48:40 [notice] 1#1: start worker process 30
2022/07/31 06:48:40 [notice] 1#1: start worker process 31

2022-07-31 06:47:53+00:00 [Note] [Entrypoint]: MySQL init process done. Ready for start up.

2022-07-31T06:47:53.837348Z 0 [Warning] [MY-011068] [Server] The syntax '--skip-host-cache' is deprecated and will be removed in a future release. Please use SET GLOBAL host_cache_size=0 instead.
2022-07-31T06:47:53.839484Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.30) starting as process 1
2022-07-31T06:47:53.846632Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2022-07-31T06:47:54.085429Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2022-07-31T06:47:54.299074Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2022-07-31T06:47:54.299125Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2022-07-31T06:47:54.301506Z 0 [Warning] [MY-011810] [Server] Insecure configuration for --pid-file: Location '/var/run/mysqld' in the path is accessible to all OS users. Consider choosing a different directory.
2022-07-31T06:47:54.325585Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /var/run/mysqld/mysqlx.sock
2022-07-31T06:47:54.325647Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.30' socket: '/var/run/mysqld/mysqld.sock' port: 330

@vaughngx4
Copy link
Contributor

@krishnakanthpps When using Docker use my fork as fixes have not been merged yet. Please read Docker.README.md carefully regarding endpoints. When using Docker only ports 80 and 443 are used.

@krishnakanthpps
Copy link
Author

Can you help me on what settings do I need to update so that I can see the installation's login and admin screens?

I did not change the BASE_DOMAIN="mydomain.example".

I am kind of lost here now.

@vaughngx4
Copy link
Contributor

@krishnakanthpps I added NGINX as a reverse proxy so you can only reach the login from https://socio.mydomain.example and https://socio.mydomain.example/admin.

You need some sort of DNS resolver to point those addresses to the IP of the machine your SocioBoard is running on. See docker/nginx/ssl/SSL.README.md for a list of subdomains.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants