Opened 12 years ago

Closed 12 years ago

#35 closed (fixed)

FOAM is down on bbn-hn

Reported by: Owned by:
Priority: major Milestone:
Component: OpenFlow Version: SPIRAL4
Keywords: Cc:


On bbn-hn, I can't connect to FOAM; I get

ERROR:omni.protogeni:Call for List Resources at failed.: Unknown socket error: [Errno 111] Connection refused

Change History (5)

comment:1 Changed 12 years ago by

When I log in to look around, I see that nginx and FOAM are running, but the nginx FOAM config fragment seems not to be enabled -- in fact, the whole /etc/nginx/sites-enabled directory is missing -- so nginx isn't listening on port 3626.

comment:2 Changed 12 years ago by

Owner: changed from somebody to

comment:3 Changed 12 years ago by

Owner: changed from to
Status: newassigned

comment:4 Changed 12 years ago by


Please give it another try; it seems to be working for me.

FYI: there's a "sites-available" directory in nginx, but there's *not* a "sites-enabled". You should be looking in /etc/nginx/conf.d - which is where nginx holds the synlink to the foam config fragment that's stored in "sites-available".

comment:5 Changed 12 years ago by

Resolution: fixed
Status: assignedclosed

It's working for me now too. Did you change anything?

Other FOAM servers have a /etc/nginx/sites-enabled directory, where the foam.conf symlink lives. Maybe this is a Red Hat thing? Mm, indeed: On an Ubuntu FOAM server, I see

[08:02:50] jbs@tulum:/home/jbs
+$ grep -i include /etc/nginx/nginx.conf
    include       /etc/nginx/mime.types;
    include /etc/nginx/conf.d/*.conf;
    include /etc/nginx/sites-enabled/*;

whereas on bbn-hn:

[12:04:10] jbs@bbn-hn:/home/jbs
+$ grep -i include /etc/nginx/nginx.conf
    include       /etc/nginx/mime.types;
#        #    include        fastcgi_params;
    include /etc/nginx/conf.d/*.conf;

So, that explains that. It might be nice if they were in synch (so people who have both a campus FOAM and an ExoGENI FOAM can find things in similar places), but that's beyond the scope of this ticket. Closing this one out.

Note: See TracTickets for help on using tickets.