[OpenIndiana-discuss] Something is disabling nfs-mapid on my server

[Adam Števko]

Hi, 

supposing it is a command, you should leave execsnoop running and check the output to find the command. After that, we might know more. 

Cheers,
Adam

> On 23 Oct 2016, at 10:38, Andreas Wacknitz <A.Wacknitz at gmx.de> wrote:
> 
> Hi,
> 
> On my freshly installed build server something is disabling nfs-mapid during night. Here are some logs:
> 
> /var/svc/log/network-nfs-mapid\:default.log:
> [ Okt 23 01:42:29 Stopping because dependency activity requires stop. ]
> [ Okt 23 01:42:29 Executing stop method (:kill). ]
> [ Okt 23 01:42:29 Executing start method ("/usr/lib/nfs/nfsmapid"). ]
> [ Okt 23 01:42:29 Method "start" exited with status 0. ]
> [ Okt 23 01:42:29 Stopping because service disabled. ]
> [ Okt 23 01:42:29 Executing stop method (:kill). ]
> 
> 
> /var/adm/messages:
> Oct 23 01:42:14 dl380g7 in.routed[1008]: [ID 755015 daemon.notice] bnx0 has a bad broadcast address 0.0.0.0
> Oct 23 01:42:14 dl380g7 in.routed[1008]: [ID 749644 daemon.notice] bnx0 has a bad address 0.0.0.0
> Oct 23 01:42:14 dl380g7 in.routed[1008]: [ID 464608 daemon.error] route 0.0.0.0/24 --> 0.0.0.0 nexthop is not directly connected
> Oct 23 01:42:14 dl380g7 in.routed[1008]: [ID 970160 daemon.notice] unable to get interface flags for bnx0: No such device or address
> Oct 23 01:42:14 dl380g7 in.ndpd[903]: [ID 169330 daemon.error] Interface bnx0 has been removed from kernel. in.ndpd will no longer use it
> Oct 23 01:42:14 dl380g7 in.routed[1008]: [ID 749644 daemon.notice] bnx0 has a bad address 0.0.0.0
> 
> 
> Logs of services that seem to be automatically touched:
> -rw-r--r--   1 root     root       28848 Okt 23 05:01 milestone-network:default.log
> -rw-r--r--   1 root     root       67991 Okt 23 06:01 network-location:default.log
> -rw-r--r--   1 root     root      148696 Okt 23 06:01 network-ipfilter:default.log
> -rw-r--r--   1 root     root       17909 Okt 23 06:01 network-dns-client:default.log
> -rw-r--r--   1 root     root       11430 Okt 23 06:01 milestone-name-services:default.log
> -rw-r--r--   1 root     root       87088 Okt 23 06:01 system-identity:domain.log
> -rw-r--r--   1 root     root       86752 Okt 23 06:01 system-name-service-cache:default.log
> -rw-r--r--   1 root     root        4720 Okt 23 06:01 network-nfs-cbd:default.log
> -rw-r--r--   1 root     root       96726 Okt 23 06:01 system-filesystem-autofs:default.log
> -rw-r--r--   1 root     root       96766 Okt 23 06:01 network-smtp:sendmail.log
> -rw-r--r--   1 root     root      100803 Okt 23 06:01 network-sendmail-client:default.log
> 
> An example of a service that is also disabled but automatically enabled later:
> /var/svc/log/network-dns-client\:default.log:
> [ Okt 23 01:42:29 Stopping because dependency activity requires stop. ]
> [ Okt 23 01:42:29 Executing start method (null). ]
> [ Okt 23 01:42:31 Stopping because service disabled. ]
> [ Okt 23 05:01:34 Enabled. ]
> 
> 
> So, unlike other services mapid stays disabled and I have to enable it manually every time.
> Does anybody have any clue how I can fix this?
> 
> Regards,
> Andreas
> 
> 
> _______________________________________________
> openindiana-discuss mailing list
> openindiana-discuss at openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss