New pod up but getting some errors


(Dan Eklund) #1

Hello!

I started my pod the other day, and it’s working, but not fully. It’s running under CentOS 7, which has caused me more problems than I was expecting since I didn’t understand the extra security restrictions of SELinux going in. I’ve worked through them, but am seeing the following errors:

[2018-12-27T13:10:11] INFO PID-5567 TID-69909489700700 Rails: Started GET “/api/statusnet/config.json” for 85.25.100.39 at 2018-12-27 13:10:11 -0500
[2018-12-27T13:10:11] FATAL PID-5567 TID-69909489700700 Rails:
[2018-12-27T13:10:11] FATAL PID-5567 TID-69909489700700 Rails: ActionController::RoutingError (No route matches [GET] “/api/statusnet/config.json”):
[2018-12-27T13:10:11] FATAL PID-5567 TID-69909489700700 Rails:
[2018-12-27T13:10:11] FATAL PID-5567 TID-69909489700700 Rails: actionpack (5.1.6) lib/action_dispatch/middleware/debug_exceptions.rb:63:in `call’

and

[2018-12-27T13:10:11] INFO PID-5570 TID-69909489700700 Rails: Started GET “/siteinfo.json” for 85.25.100.39 at 2018-12-27 13:10:11 -0500
[2018-12-27T13:10:11] FATAL PID-5570 TID-69909489700700 Rails:
[2018-12-27T13:10:11] FATAL PID-5570 TID-69909489700700 Rails: ActionController::RoutingError (No route matches [GET] “/siteinfo.json”):
[2018-12-27T13:10:11] FATAL PID-5570 TID-69909489700700 Rails:
[2018-12-27T13:10:11] FATAL PID-5570 TID-69909489700700 Rails: actionpack (5.1.6) lib/action_dispatch/middleware/debug_exceptions.rb:63:in `call’

As well as other similar failed GETs. I suspect a permissions issue but haven’t found the smoking gun yet.

The pod is at https://weare.boldlygoingnowhere.org/ if that helps.

Thanks!


(Benjamin Neff) #2

That isn’t a problem, that’s just something crawling URLs which don’t exist.


(Dan Eklund) #3

Excellent! Thanks. I really appreciate your help.