Jump to content


Photo

H2400 PLi6.0 Geen samba na opstart

Started by doglover, 27 Oct 2017 08:44

  • Please log in to reply
90 replies to this topic

Re: H2400 PLi6.0 Geen samba na opstart #61 doglover

  • Rytec EPG Team
  • 17,407 posts

+658
Excellent

Posted 11 April 2018 - 06:43

Deze ochtend is hij normaal opgestart.  Maar ik ben de opstart log al kwijt, omdat de log level =3 zoveel output genereerd dat de oude files al weg waren vooraleer ik eraan kwam.

 

Zal in de loop van de dag nog wel de kans hebben.

 

Willy


~~Rytec Team~~
Maxytec Multibox SE OpenPli (used as mediaplayer)
Mutant HD2400 OpenPli
Vu+ Duo OpenPli (backup)

Synology NAS

Sat: 13E, 19.2E, 23.5E and 28.2E
*Pli/Rytec EPG POWERED*

Re: H2400 PLi6.0 Geen samba na opstart #62 doglover

  • Rytec EPG Team
  • 17,407 posts

+658
Excellent

Posted 11 April 2018 - 06:56

Toch maar eens opnieuw gestart:

[1970/01/01 01:00:30.240276,  3] ../source3/param/loadparm.c:3742(lp_load_ex)
  lp_load_ex: refreshing parameters
[1970/01/01 01:00:30.241404,  3] ../source3/param/loadparm.c:544(init_globals)
  Initialising global parameters
[1970/01/01 01:00:30.242103,  2] ../source3/param/loadparm.c:316(max_open_files)
  rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
[1970/01/01 01:00:30.244016,  3] ../source3/param/loadparm.c:2671(lp_do_section)
  Processing section "[global]"
[1970/01/01 01:00:30.247667,  2] ../source3/param/loadparm.c:2688(lp_do_section)
  Processing section "[root]"
[1970/01/01 01:00:30.259123,  2] ../source3/param/loadparm.c:2688(lp_do_section)
  Processing section "[Media]"
[1970/01/01 01:00:30.262359,  2] ../source3/param/loadparm.c:2688(lp_do_section)
  Processing section "[Harddisk]"
[1970/01/01 01:00:30.268744,  3] ../source3/param/loadparm.c:1588(lp_add_ipc)
  adding IPC service
[1970/01/01 01:00:30.278259,  2] ../source3/lib/interface.c:345(add_interface)
  added interface eth0 ip=192.168.178.15 bcast=192.168.178.255 netmask=255.255.255.0
[1970/01/01 01:00:30.288027,  3] ../source3/smbd/server.c:1448(main)
  loaded services
[1970/01/01 01:00:30.304531,  1] ../source3/profile/profile_dummy.c:30(set_profile_level)
  INFO: Profiling support unavailable in this build.
[1970/01/01 01:00:30.306258,  3] ../source3/smbd/server.c:1467(main)
  Standard input is not a socket, assuming -D option
[1970/01/01 01:00:30.306750,  3] ../source3/smbd/server.c:1479(main)
  Becoming a daemon.
[1970/01/01 01:00:30.357345,  2] ../source3/passdb/pdb_interface.c:160(make_pdb_method_name)
  No builtin backend found, trying to load plugin
[1970/01/01 01:00:30.495689,  2] ../lib/util/modules.c:196(do_smb_load_module)
  Module 'tdbsam' loaded
[1970/01/01 01:00:30.957967,  3] ../source3/auth/token_util.c:547(finalize_local_nt_token)
  Failed to fetch domain sid for WORKGROUP
[1970/01/01 01:00:30.960778,  3] ../source3/auth/token_util.c:579(finalize_local_nt_token)
  Failed to fetch domain sid for WORKGROUP
[1970/01/01 01:00:31.145980,  3] ../source3/rpc_server/svcctl/srv_svcctl_reg.c:565(svcctl_init_winreg)
  Initialise the svcctl registry keys if needed.
[1970/01/01 01:00:31.448834,  3] ../source3/rpc_server/eventlog/srv_eventlog_reg.c:59(eventlog_init_winreg)
  Initialise the eventlog registry keys if needed.
[1970/01/01 01:00:31.473612,  0] ../lib/util/become_daemon.c:124(daemon_ready)
  STATUS=daemon 'smbd' finished starting up and ready to serve connections
[1970/01/01 01:00:31.645162,  2] ../source3/smbd/server.c:1125(smbd_parent_loop)
  waiting for connections
[2018/04/11 07:51:18.590389,  2] ../source3/smbd/server.c:576(remove_child_pid)
  Could not find child 479 -- ignoring
[2018/04/11 07:53:12.316815,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:13.082275,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:13.942503,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:14.692228,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:15.457291,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:16.317023,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:17.067117,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:17.816791,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:18.676482,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:19.426072,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:20.176143,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:21.052416,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:21.816783,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:22.567365,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:25.660952,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:26.426075,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:27.176105,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:27.927054,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:28.691754,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:29.441801,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:34.723305,  3] ../source3/nmbd/nmbd_incomingrequests.c:323(process_node_status_request)
  process_node_status_request: status request for name *<00> from IP 192.168.178.37 on subnet UNICAST_SUBNET.
[2018/04/11 07:53:39.170200,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:39.769698,  3] ../source3/nmbd/nmbd_incomingrequests.c:323(process_node_status_request)
  process_node_status_request: status request for name *<00> from IP 192.168.178.37 on subnet UNICAST_SUBNET.
[2018/04/11 07:53:39.929142,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:40.676100,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:41.536252,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:42.291653,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:43.041691,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:43.910848,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:44.660429,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:45.410443,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:46.286098,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:47.035754,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:47.801103,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:48.664090,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:49.414007,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:50.176148,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:51.036057,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:51.801178,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:53:52.551062,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:54:00.215231,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:54:00.957389,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:54:01.723059,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:54:02.474009,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:54:03.223356,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:54:03.973052,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:54:09.167471,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:54:09.910465,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:54:10.661075,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>
[2018/04/11 07:54:11.536219,  3] ../source3/nmbd/nmbd_incomingrequests.c:459(process_name_query_request)
  process_name_query_request: Name query from 192.168.178.17 on subnet 192.168.178.15 for name BRW34238763B77E<00>

Dit is wat ik vind na een startup, en samba connecteerd.  (Mijn PC runde wel al - 192.168.178.17)

 

Willy


~~Rytec Team~~
Maxytec Multibox SE OpenPli (used as mediaplayer)
Mutant HD2400 OpenPli
Vu+ Duo OpenPli (backup)

Synology NAS

Sat: 13E, 19.2E, 23.5E and 28.2E
*Pli/Rytec EPG POWERED*

Re: H2400 PLi6.0 Geen samba na opstart #63 WanWizard

  • PLi® Core member
  • 70,551 posts

+1,813
Excellent

Posted 11 April 2018 - 10:22

De issue is dit:

[1970/01/01 01:00:34.138289,  1] ../source3/lib/messages_dgm.c:157(messaging_dgm_lockfile_create)
  messaging_dgm_lockfile_create: write failed: Invalid argument
[1970/01/01 01:00:34.140900,  1] ../source3/lib/messages_dgm.c:228(messaging_dgm_init)
  messaging_dgm_init: messaging_dgm_create_lockfile failed: Invalid argument
[1970/01/01 01:00:34.141349,  2] ../source3/lib/messages.c:409(messaging_reinit)
  messaging_dgm_ref failed: Invalid argument
[1970/01/01 01:00:34.141988,  0] ../source3/lib/util.c:478(reinit_after_fork)
  messaging_reinit() failed: NT_STATUS_INVALID_PARAMETER
[1970/01/01 01:00:34.142398,  0] ../lib/util/become_daemon.c:111(exit_daemon)
  STATUS=daemon failed to start: reinit_after_fork() failed, error code 22

De vraag is nu, wat is dit precies, en waarom. Daarvoor zullen we de source in moeten.

 

Kun je in de gaten houden, de volgende keer als het weer niet start, of de foutmeldingen dezelfde zijn?


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.

Re: H2400 PLi6.0 Geen samba na opstart #64 doglover

  • Rytec EPG Team
  • 17,407 posts

+658
Excellent

Posted 12 April 2018 - 13:03

Deze middag was het weer prijs:

[1970/01/01 01:00:35.073636,  2] ../source3/lib/tallocmsg.c:56(register_msg_pool_usage)
  Registered MSG_REQ_POOL_USAGE
[1970/01/01 01:00:35.075265,  2] ../source3/lib/dmallocmsg.c:78(register_dmalloc_msgs)
  Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
[1970/01/01 01:00:35.077136,  3] ../source3/param/loadparm.c:3742(lp_load_ex)
  lp_load_ex: refreshing parameters
[1970/01/01 01:00:35.078275,  3] ../source3/param/loadparm.c:544(init_globals)
  Initialising global parameters
[1970/01/01 01:00:35.078974,  2] ../source3/param/loadparm.c:316(max_open_files)
  rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
[1970/01/01 01:00:35.080917,  3] ../source3/param/loadparm.c:2671(lp_do_section)
  Processing section "[global]"
[1970/01/01 01:00:35.085016,  3] ../source3/nmbd/nmbd.c:414(reload_nmbd_services)
  services not loaded
[1970/01/01 01:00:35.089080,  3] ../source3/nmbd/nmbd.c:953(main)
  standard input is not a socket, assuming -D option
[1970/01/01 01:00:35.089767,  3] ../source3/nmbd/nmbd.c:958(main)
  Becoming a daemon.
[1970/01/01 01:00:35.123712,  1] ../source3/lib/messages_dgm.c:157(messaging_dgm_lockfile_create)
  messaging_dgm_lockfile_create: write failed: Invalid argument
[1970/01/01 01:00:35.124950,  1] ../source3/lib/messages_dgm.c:228(messaging_dgm_init)
  messaging_dgm_init: messaging_dgm_create_lockfile failed: Invalid argument
[1970/01/01 01:00:35.125386,  2] ../source3/lib/messages.c:409(messaging_reinit)
  messaging_dgm_ref failed: Invalid argument
[1970/01/01 01:00:35.126025,  0] ../source3/lib/util.c:478(reinit_after_fork)
  messaging_reinit() failed: NT_STATUS_INVALID_PARAMETER
[1970/01/01 01:00:35.136897,  0] ../lib/util/become_daemon.c:111(exit_daemon)
  STATUS=daemon failed to start: reinit_after_fork() failed, error code 22

Dus dezelfde fout melding.

 

Willy


~~Rytec Team~~
Maxytec Multibox SE OpenPli (used as mediaplayer)
Mutant HD2400 OpenPli
Vu+ Duo OpenPli (backup)

Synology NAS

Sat: 13E, 19.2E, 23.5E and 28.2E
*Pli/Rytec EPG POWERED*

Re: H2400 PLi6.0 Geen samba na opstart #65 WanWizard

  • PLi® Core member
  • 70,551 posts

+1,813
Excellent

Posted 12 April 2018 - 13:53

Dit is OpenPLi 6, toch?

 

Wat ik dan even niet snap: "source3" is de source tree voor Samba v3, en in OpenPLi 6 draait Samba v4.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.

Re: H2400 PLi6.0 Geen samba na opstart #66 doglover

  • Rytec EPG Team
  • 17,407 posts

+658
Excellent

Posted 12 April 2018 - 14:30

Neen dit is OpenPLi 6.1

Op de HD2400 draait OpenPLi 6

 

Willy


Edited by doglover, 12 April 2018 - 14:30.

~~Rytec Team~~
Maxytec Multibox SE OpenPli (used as mediaplayer)
Mutant HD2400 OpenPli
Vu+ Duo OpenPli (backup)

Synology NAS

Sat: 13E, 19.2E, 23.5E and 28.2E
*Pli/Rytec EPG POWERED*

Re: H2400 PLi6.0 Geen samba na opstart #67 WanWizard

  • PLi® Core member
  • 70,551 posts

+1,813
Excellent

Posted 12 April 2018 - 14:34

Apart.

 

Moet er nog eens diep over nadenken, ik heb ik de code zitten zoeken, maar ik kan niet vinden wat er mis zou kunnen zijn met die lockfile.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.

Re: H2400 PLi6.0 Geen samba na opstart #68 WanWizard

  • PLi® Core member
  • 70,551 posts

+1,813
Excellent

Posted 23 April 2018 - 21:10

Willy,

 

Ik neem aan dat dit probleem nog steeds speelt?

 

Indien dat zo is, kun je in /etc/rc3.d "S20samba.sh" renamen naar "S30samba.sh". We denken dat samba te snel start, en soms tmpfs nog niet operationeel is, waardoor het aanmaken van de lockfile mislukt.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.

Re: H2400 PLi6.0 Geen samba na opstart #69 doglover

  • Rytec EPG Team
  • 17,407 posts

+658
Excellent

Posted 24 April 2018 - 07:00

Is idd nog steeds aanwezig.

Zal de file renamen.  Alleen begrijp ik niet dat met een naam wijziging samba later start.

 

Willy


Edited by doglover, 24 April 2018 - 07:03.

~~Rytec Team~~
Maxytec Multibox SE OpenPli (used as mediaplayer)
Mutant HD2400 OpenPli
Vu+ Duo OpenPli (backup)

Synology NAS

Sat: 13E, 19.2E, 23.5E and 28.2E
*Pli/Rytec EPG POWERED*

Re: H2400 PLi6.0 Geen samba na opstart #70 littlesat

  • PLi® Core member
  • 57,186 posts

+699
Excellent

Posted 24 April 2018 - 07:27

S30 is hoger dan s20 vandaar...

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W

Re: H2400 PLi6.0 Geen samba na opstart #71 doglover

  • Rytec EPG Team
  • 17,407 posts

+658
Excellent

Posted 24 April 2018 - 07:35

Heb mij wat ingelezen, en dit gevonden:

 

Now, the naming scheme is also quite simple. Scripts whose name begins with an S will be started at the runlevel in question while those whose name begins with K will be killed. Notice that all the scripts in rc6.d, the reboot runlevel, start with K. That's because they should all be stoped for a reboot and nothing should be started. The numbers refer to the running order of the scripts. Those with smaller numbers will be run before those with higher numbers. So, in your specific example, S23ntp will be run (started in this case) before S24dovecot.

 

 

Begrepen nu.

 

Willy


~~Rytec Team~~
Maxytec Multibox SE OpenPli (used as mediaplayer)
Mutant HD2400 OpenPli
Vu+ Duo OpenPli (backup)

Synology NAS

Sat: 13E, 19.2E, 23.5E and 28.2E
*Pli/Rytec EPG POWERED*

Re: H2400 PLi6.0 Geen samba na opstart #72 Tech

  • Forum Moderator
    PLi® Core member
  • 14,925 posts

+486
Excellent

Posted 24 April 2018 - 13:18

Je geeft op die manier een (volgorde) prioriteit aan, Sxx (hoe hoger xx des te later iets start) staat voor opstarten Kxx voor het afsluiten.

Aan de rand van de afgrond is een stap voorwaarts niet altijd vooruitgang....

On the edge of the abyss, a step forward is not always progress....

Hardware: 2x Daily used Vu+ Ultimo 4K - Vu+ Duo 4K SE and a lot more.... - VisioSat BiBigsat - Jultec Unicable Multiswitch 4 positions: 19.2/23.5/28.2 East - Diseqc motorized flatdish antenna

Software : HomeBuild OpenPLi Develop and Scarthgap builds, local cards driven by OsCam

Press the Geplaatste afbeelding button on the buttom right of this message ;)

Have you tried our wiki yet? Many answers can be found in our OpenPLi wiki

Re: H2400 PLi6.0 Geen samba na opstart #73 doglover

  • Rytec EPG Team
  • 17,407 posts

+658
Excellent

Posted 26 April 2018 - 08:43

Resultaten:

 

HD2400: 3 reboots - allen hadden samba running.  Dus geen probleem hier.

 

ZGemma: 5 reboots waarvan in 3 gevallen samba normaal werkte, en in 2 gevallen nmdb gecrasht was en dus samba niet werkte.

 

 

Ik blijf het verder monitoren. 

 

Willy

 

PS: de Zgemma is minder belangrijk hier, daarom had ik in eerste instantie er minder aandacht voor.  Op deze Zgemma is er geen softcam die moet starten (en zoals ik gezien heb start de softcam voor samba)


~~Rytec Team~~
Maxytec Multibox SE OpenPli (used as mediaplayer)
Mutant HD2400 OpenPli
Vu+ Duo OpenPli (backup)

Synology NAS

Sat: 13E, 19.2E, 23.5E and 28.2E
*Pli/Rytec EPG POWERED*

Re: H2400 PLi6.0 Geen samba na opstart #74 WanWizard

  • PLi® Core member
  • 70,551 posts

+1,813
Excellent

Posted 26 April 2018 - 11:51

Merci.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.

Re: H2400 PLi6.0 Geen samba na opstart #75 doglover

  • Rytec EPG Team
  • 17,407 posts

+658
Excellent

Posted 26 April 2018 - 12:25

Je zult zien dat na een post zoals hierbovedn, het net devolgende keer fout gaat:

 

Net de Zgemma opgestart na de middagpauze, en natuurlijk geen samba......

 

E.e.a is dus nog niet gevonden.

 

Willy

 

PS: Heb daqn maar een work-around geconfigureerd.  Een verbinding via FTP in explorer werkt altijd.


~~Rytec Team~~
Maxytec Multibox SE OpenPli (used as mediaplayer)
Mutant HD2400 OpenPli
Vu+ Duo OpenPli (backup)

Synology NAS

Sat: 13E, 19.2E, 23.5E and 28.2E
*Pli/Rytec EPG POWERED*

Re: H2400 PLi6.0 Geen samba na opstart #76 WanWizard

  • PLi® Core member
  • 70,551 posts

+1,813
Excellent

Posted 27 April 2018 - 22:17

Willy,

 

Zou je in /etc/init.d/samba.sh, direct onder "start)" de volgende regel willen zetten:

[ -d /var/lib/samba/msg.lock ] && rm -rf /var/lib/samba/msg.lock

we denken dat dit het opstart probleem oplost. Zou je dat willen testen?


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.

Re: H2400 PLi6.0 Geen samba na opstart #77 doglover

  • Rytec EPG Team
  • 17,407 posts

+658
Excellent

Posted 28 April 2018 - 07:42

Deze ochtend was het weer prijs.  Geen samba op de Zgemma.

 

Heb de regel erin gezet.

 

Willy


~~Rytec Team~~
Maxytec Multibox SE OpenPli (used as mediaplayer)
Mutant HD2400 OpenPli
Vu+ Duo OpenPli (backup)

Synology NAS

Sat: 13E, 19.2E, 23.5E and 28.2E
*Pli/Rytec EPG POWERED*

Re: H2400 PLi6.0 Geen samba na opstart #78 WanWizard

  • PLi® Core member
  • 70,551 posts

+1,813
Excellent

Posted 28 April 2018 - 13:42

Merci, we zijn reuze benieuwd.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.

Re: H2400 PLi6.0 Geen samba na opstart #79 doglover

  • Rytec EPG Team
  • 17,407 posts

+658
Excellent

Posted 29 April 2018 - 09:32

Een vraagje om mijn bash scripting kennis wat op te vijzelen:

 

Wat doet dit precies:

[ -d /var/lib/samba/msg.lock ] && rm -rf /var/lib/samba/msg.lock

rm -rf /var/lib/samba/msg.lock

Kan ik begrijpen: dat wist de folder /var/lib/samba/msg.lock recursively and without a question asked.

 

[ -d /var/lib/samba/msg.lock ]

 

begrijp ik niet.  Als het gebruikt wordt in een if ... fi statement dan checkt het voor het bestaan van de folder.  Als de folder bestaat is het antwoord True.

Maar zonder de if ... fi  ben ik de draad kwijt.

 

En dan de combinatie van beide statements is ook een vraagteken voor mij.

 

Willy


~~Rytec Team~~
Maxytec Multibox SE OpenPli (used as mediaplayer)
Mutant HD2400 OpenPli
Vu+ Duo OpenPli (backup)

Synology NAS

Sat: 13E, 19.2E, 23.5E and 28.2E
*Pli/Rytec EPG POWERED*

Re: H2400 PLi6.0 Geen samba na opstart #80 WanWizard

  • PLi® Core member
  • 70,551 posts

+1,813
Excellent

Posted 29 April 2018 - 11:44

Het maakt gebruik van boolean evaluation.

 

Als je wilt weten of "a && b" true is, en "a" is true, dan moet je "b" evalueren om te weten of de hele expressie true is. Is "a" echter false, dan weet je genoeg, en hoef je niet meer naar "b" te kijken.

 

In bovenstaande expressie, als de directory bestaat (test is true), dan moet het commando worden uitgevoerd. Als de directory niet bestaat (test is false), dan wordt het commando overgeslagen. 

 

Een soortgelijke constructie kun je ook omdraaien, door midden van een "or" in plaats van een "and", b.v.

[ -d /tmp/test ] || mkdir /tmp/test

Als je wilt weten of "a || b" true is, en "a" is true, dan weet je genoeg, en hoef je niet meer naar "b" te kijken. Is "a" echter false, dan moet je "b" evalueren om te weten of de hele expressie true is.

 

Dus, als de directory niet besstaat (test is false), dan wordt de directory aangemaakt.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.

Back to [NL] Gebruikersondersteuning

10 user(s) are reading this topic

0 members, 10 guests, 0 anonymous users

  1. Forums
  2. → PLi® Support
  3. → [NL] Gebruikersondersteuning