nmis selftest error

 
1
0
-1

i changed group to nmis but still not working.

 

    CommentAdd your comment...

    2 answers

    1.  
      1
      0
      -1

      i run it but it only clear them for few minutes after that. it shows them again. another is that after performing that command. it gave me the following output. how do i clear them for good.

       

      [root@saturn ~]# sudo /usr/local/nmis8/admin/fixperms.pl

      This script will fix the permissions for NMIS based on the configuration /home/nmis/admin/../conf/Config.nmis

      The directory to be processed is: /home/nmis

      The user will be set to: nmis

      The group will be set to: nmis

      chown: changing ownership of `/home/nmis/var/lepini.eskom.co.za-Config-collect.lock': No such file or directory

      chown: changing ownership of `/home/nmis/var/lewensaar.eskom.co.za-Config-collect.lock': No such file or directory

      chown: changing ownership of `/home/nmis/var/douglas_tsc.eskom.co.za-Config-collect.lock': No such file or directory

      chown: changing ownership of `/home/nmis/var/drakensberg-dcn.eskom.co.za-Config-collect.lock': No such file or directory

      chown: changing ownership of `/home/nmis/var/dinaledi.eskom.co.za-Config-collect.lock': No such file or directory

      chown: changing ownership of `/home/nmis/var/dutoits.eskom.co.za-Config-collect.lock': No such file or directory

      chown: changing ownership of `/home/nmis/var/driefontein.eskom.co.za-Config-collect.lock': No such file or directory

      chown: changing ownership of `/home/nmis/var/ludeke_ss.eskom.co.za-Config-collect.lock': No such file or directory

      chown: changing ownership of `/home/nmis/var/poseidon_switch.eskom.co.za-Config-collect.lock': No such file or directory

      chown: changing ownership of `/home/nmis/var/polokwanevc.eskom.co.za-Config-collect.lock': No such file or directory

      chown: changing ownership of `/home/nmis/var/lomond.eskom.co.za-Config-collect.lock': No such file or directory

      chown: changing ownership of `/home/nmis/var/port_nollorth-Config-collect.lock': No such file or directory

      chown: changing ownership of `/home/nmis/var/libertas.eskom.co.za-Config-collect.lock': No such file or directory

      chown: changing ownership of `/home/nmis/var/droerivier_rr.eskom.co.za-Config-collect.lock': No such file or directory

      chown: changing ownership of `/home/nmis/var/pretoria_rs.eskom.co.za-Config-collect.lock': No such file or directory

      chown: changing ownership of `/home/nmis/var/port_elizabeth_office_switch.eskom.co.za-Config-collect.lock': No such file or directory

      chown: changing ownership of `/home/nmis/var/dryhurst.eskom.co.za-Config-collect.lock': No such file or directory

      chown: changing ownership of `/home/nmis/var/pinetown.eskom.co.za-Config-collect.lock': No such file or directory

      chown: changing ownership of `/home/nmis/var/ducats.eskom.co.za-Config-collect.lock': No such file or directory

      chown: changing ownership of `/home/nmis/var/diamond.eskom.co.za-Config-collect.lock': No such file or directory

      chown: changing ownership of `/home/nmis/var/lethabo-distr-Config-collect.lock': No such file or directory

      chmod: cannot access `/home/nmis/var/nmc-dcn-sf-d-02-Config-collect.lock': No such file or directory

      chmod: cannot access `/home/nmis/var/newgate_sub.eskom.co.za-Config-collect.lock': No such file or directory

      chmod: cannot access `/home/nmis/var/normandie.eskom.co.za-Config-collect.lock': No such file or directory

      chmod: cannot access `/home/nmis/var/newthabazimbi_switch.eskom.co.za-Config-collect.lock': No such file or directory

      chmod: cannot access `/home/nmis/var/nevis.eskom.co.za-Config-collect.lock': No such file or directory

      chmod: cannot access `/home/nmis/var/nondabuya ss-Config-collect.lock': No such file or directory

      chmod: cannot access `/home/nmis/var/nkangala.eskom.co.za-Config-collect.lock': No such file or directory

       

       

      1. Alexander Zangerl

        fixperms not being able to change collect or update lock files is mostly benign, it means you started the fixperms while a collect was running, fixperms found these files to check and fix but when it got through its list those temporary lock files were gone (as the collect had finished). however, it looks like your nmis is configured inconsistently: the setting for '<nmis_base>' in conf/Config.nmis says '/home/nmis' , but you're running your programs out of '/usr/local/nmis8'. running nmis outside of /usr/local/nmis8 is not a currently supported configuration - in general it should work, but you're on your own. check whether /usr/local/nmis8 is identical to /home/nmis. if not choose one, ditch the other and make it into a symlink.

      2. bahedile mogaadile

        will reinstalling the same upgrade resolve inconsistency you mentioned above? i have check all but could not find it. will the backup that system created work again from my last installation?

      3. bahedile mogaadile

        nmis selftest permission is now resolved.

      CommentAdd your comment...
    2.  
      1
      0
      -1

      nmis 8.6 is more precise and strict about permissions, which is why you see these now after the upgrade.

      you should run sudo /usr/local/nmis8/admin/fixperms.pl  to have it adjust the permissions in one go, then click the 'reset selftest' button. (the selftest does permission checks only once every 2 hours for performance reasons, and you certainly won't want to wait that long)

        CommentAdd your comment...