Network Management

last person joined: 18 hours ago 

Keep an informative eye on your network with HPE Aruba Networking network management solutions
Expand all | Collapse all

not able to connect to airwave

This thread has been viewed 13 times
  • 1.  not able to connect to airwave

    Posted Dec 13, 2013 12:48 PM

    hi

     

    i am not able to connect to airwave using https or http. the server is running and it is sending alert message. but i am not able to connect to the interface. any help on this will be appreciated.

     

    Karthik



  • 2.  RE: not able to connect to airwave
    Best Answer

    EMPLOYEE
    Posted Dec 13, 2013 01:50 PM

    can you SSH as root to the server?  Issue the command "daemons" There should be a long list.  Try restarting them with the command "rd"



  • 3.  RE: not able to connect to airwave

    EMPLOYEE
    Posted Dec 13, 2013 01:54 PM

    Though restarting daemons is like hammering your way through the problem.  If you want to debug and find out the cause, it'd be worth opening a case with support.  Any crashes in the apache logs (/var/log/httpd/error_log or access_log)?



  • 4.  RE: not able to connect to airwave

    Posted Dec 13, 2013 02:13 PM

    [root@bhusd mercury]# daemons ?
      PID  PPID  PGID %CPU %MEM   RSS     ELAPSED CMD
     1751     1  1750  0.3  2.9 232644   20:06:52 VisualRF
     1464     1  1464  0.0  0.1 10912    20:08:11 Daemon::LowLevelServiceWatcher
     1521     1  1478  0.0  0.0   504    20:07:55 msgHandler
     1164     1  1164  0.0  0.0  1640    20:10:39 rrdcached
     1738     1  1738  0.0  2.9 230716   20:06:53 snmptrapd

     

    i dont see a long list just the above



  • 5.  RE: not able to connect to airwave

    Posted Dec 13, 2013 02:17 PM

    What is the output of # df -h

     

    i guess the server is out of disk space

     

     



  • 6.  RE: not able to connect to airwave

    Posted Dec 13, 2013 04:52 PM

    [root@bhusd mercury]# df -h
    Filesystem            Size  Used Avail Use% Mounted on
    /dev/mapper/VolGroup00-LogVol00
                           65G   14G   48G  23% /
    tmpfs                 3.8G     0  3.8G   0% /dev/shm
    /dev/sda1              97M   36M   57M  39% /boot

     

    have enough disk space



  • 7.  RE: not able to connect to airwave

    EMPLOYEE
    Posted Dec 13, 2013 04:56 PM

    Did you try 'restart daemons' ('rd' command) already?  If not, go ahead and do so and open a support case to see if they can help find the root cause.



  • 8.  RE: not able to connect to airwave

    Posted Dec 13, 2013 05:29 PM

    i did and below is the output

     and also i am able to connect to the interface .. thanks a lot for the help...and how do i enable autoboot...i restarted the server before running rd.. but the server is not doing autoboot. it stops in the boot prompt then i need to press enter to boot..please help me on this too.

    [root@bhusd mercury]# daemons
      PID  PPID  PGID %CPU %MEM   RSS     ELAPSED CMD
     2218     1  2218  0.0  0.2 18716       02:08 airbus
     1924     1  1924 33.7 10.4 820716      03:18 httpd_
     2212     1  2212  1.1 10.3 815392      02:09 Daemon::ServiceWatcher
     2220     1  2220  0.0 10.3 814092      02:08 Daemon::PortGrabber
     2223     1  2223  0.0 10.3 814036      02:07 Daemon::TupleSpaces
     2226     1  2226  0.0 10.3 814092      02:07 Daemon::TupleScheduler
     2254     1  2254  0.0 10.3 814692      02:06 Daemon::SwarmHandler
     2272     1  2272  0.3 10.3 814984      02:04 Daemon::PerfCollector
     2276     1  2276  0.0 10.3 813776      02:04 Daemon::AlertD
     2283     1  2283  0.9 10.3 815404      02:03 Daemon::APListCacher
     2286     1  2286  0.0 10.3 814520      02:03 Daemon::APScanner
     2289     1  2289  0.0 10.3 813872      02:03 Daemon::APWatcher
     2293     1  2293  0.0 10.3 814044      02:02 Daemon::APWatcherPollNow
     2296     1  2296  0.0 10.3 814580      02:02 Daemon::AsyncLoggerClient
     2299     1  2299  0.0 10.3 813784      02:01 Daemon::ConfigPusher
     2306     1  2306  0.0 10.3 814048      02:01 Daemon::ConfigVerifier
     2310     1  2310  0.0 10.3 814512      02:00 Daemon::DeviceEvent
     2317     1  2317  0.0 10.3 814072      02:00 Daemon::DNSFetcher
     2333     1  2333  0.0 10.3 814020      01:59 Daemon::PartialConfigPusher
     2336     1  2336  0.0 10.4 818936      01:59 Daemon::PAPI
     2339  2336  2336  0.0 10.3 814464      01:59 Daemon::AMONAggregator
     2375     1  2375  0.0 10.3 813812      01:54 Daemon::SNMPEnabler
     2378     1  2378  0.0 10.3 814076      01:54 Daemon::SNMPFetcher
     2384     1  2384  0.0 10.3 814952      01:14 Daemon::SNMPV2Fetcher
     2387     1  2387  0.0 10.3 814952      01:14 Daemon::SNMPV2Fetcher
     2390     1  2390  0.3 10.4 817704      01:14 Daemon::SyncD
     2397     1  2397  0.0 10.3 813812      01:13 Daemon::WepKeySetter
     2437     1  2437  0.0 10.3 815408      01:11 Daemon::AsyncLoggerClient
     2395  2394  2394 25.7  2.1 169708      01:13 VisualRF
     2200     1  2200  0.3  0.1 10268       02:12 Daemon::LowLevelServiceWatcher
     2257     1  2212  0.0  0.0   504       02:06 msgHandler
     2266     1  2266  0.0  0.0   900       02:04 pound
     2268  2266  2266  0.1  0.0  4332       02:04 pound
     2366     1  2366  0.0  1.0 85668       01:54 radiusd
     1115     1  1115  0.0  0.0  1196       06:30 rrdcached
     2382     1  2382  0.0  2.9 230600      01:14 snmptrapd



  • 9.  RE: not able to connect to airwave

    EMPLOYEE
    Posted Dec 13, 2013 02:17 PM

    It would seem that none of the other daemons are currently running on your server.  Check to see if the disk drive of the AMP is full:

    # df -h

    If it's not, then doing the 'rd' that Seth suggested could possibly get you back up and running.  But the fact that apache/pound are not visible explains why the UI was unreachable.  There may be better clues to the outtage in /var/log/low_level_service_watcher or service_watcher logs.