Unable to login in fresh napp-it install on OmniOs

[ebuceci]

Hi,

I'm not entirely new to this but stuck on the fresh reinstall of my napp-it box.
I decided it's time to switch to OmniOs (had it previously running on an osol built 134 and an old napp-it 0.8?? for years now ...)

I installed OmniOS-10b9c79 from 09/2014 (the current stable), set up the NICs, routing, dns and an user for admin purposes including sudo..
The napp-it (0.9f3) installer gave me some oops:

...
3.3 copy data /web-gui/data_0.9f3/. /var/web-gui/data/
cp: cannot stat ‘/root/web-gui/data_0.9f3/tools/mbuffer/*’: No such file or directory
chmod: cannot access ‘/usr/sbin/mbuffer’: No such file or directory

3.4 setup mini-httpd

/var/web-gui/data/tools/httpd/napp-it-mhttpd: started as root without requesting chroot(), warning only

Server available at http://127.0.0.1:3000.
...

the it told me:
-thats it, have fun
-connect your browser to http://serverip:81

which I did - the webgui came up but I'm unable to login as admin with empty password for the first time, hmmm...

Besides a new folder-structure (compared to my old version) there is no napp-it.cfg file wich I could delete to remove any config and previously set passwords...

I set up an other box last year around the early november timeframe for a co-worker of me which worked fine (was the same omnios built and I guess the same napp-it version).

Where does napp-it write its logs for the login process - didn't find any nor /var/log/syslog ?

Any help is greatly appreciated.
Thanks

Frank

 

[gea]

the setup process with OmniOS:

- install OmniOS
- login as root (and do the next steps as root)

- setup your network manually, see napp-it // webbased ZFS NAS/SAN appliance for OmniOS, OpenIndiana, Solaris and Linux : OmniOS
- run the wget installer to setup napp-it with all needed settings and tools

- open you browser and enter http://serverip:81
first login: admin without a pw

your questions
3.3 mbuffer is currently not used by napp-it
3.4 this is the default startup message of minihttpd (webserver used by napp-it, port 81)
server available at 127.0.0.1:3000, this is the mojolicious html5 websocket server for realtime graphs

the setup log and the installer is in /root
napp-it.cfg, see /var/web-gui/_log/napp-it.cfg
where you can reset passwords (delete pw hash value for admin)

do not modify/ install sudo
all what is needed is done by the napp-it installer

 

[ebuceci]

Hi gea,

thanks for the quick reply. Yepp I found the setup log there but NO the /var/web-gui/_log/napp-it.cfg isn' there
meister@gizmo:/export/home/meister$ cat /var/web-gui/_log/napp-it.cfg
cat: /var/web-gui/_log/napp-it.cfg: No such file or directory

And yes i tried - as I said before - to login via web as admin without any pw at all but it just prompts me the login page again and says:
Info:
First login: admin, no password; delete napp-it.cfg to get defaults

Please do not disable Javascript...

-adminpw disabled !!
-operatorpw disabled !!

So, is there a log for the running napp-it that actually shows login attempts, errors etc. Does it log anywhere ?

BTW. I use sudo because I need to have administrative access via ssh from outside my network and I don't wanna bother with pfexec and the solaris rbac style privilege stuff 'cuz I'm mostly an linux/bsd/osx guy. So ssh in as normal user and then sudo STUFF is the natural way for me to go and root is the last resort for local console if every other way is lost.

Thanks,
Frank

 

[gea]

After a fresh setup there is no napp-it.cfg.
The config file is created on menu About >> settings after the first login.

-adminpw disabled !!
shows that there is no admin-pw defined.

If you cannot login without a pw, then then the config is messed up.
I suppose it is your sudo modification as napp-it use sudo as well and it does all settings on setup.

What I would do:
- redo your setup from scratch, you do not need any special setups and sudo is working

After setup you can define allowed users for SSH in menu Services >> SSH >> Allow users.
In this SSH menu you can also allow root to login via ssh (perfect if you want to use WinSCP as a filebrowser)