• Into the furnace

    From Vk3jed@21:1/109 to All on Fri Jan 4 18:07:57 2019
    Well, the weather gods have pulled out a shocker for us here today. Forecast top of 45C (113F), winds 40 km/h (35 mph) gusting to 65 km/h (41 mph), RH 9%, with an unstable atmosphere and a late change.

    The setup is broadly similar to Black Saturday, though there's a little less low pressure around, making the pressure gradient a bit less, which will lower the wind speed a bit from that day. But these conditions are still bad enough to push the fire danger index (FDI) to the mid 90s for forest and over 115 for grasslands), whicd corresponds to a fire danger rating in the high end of "Extreme" - Yes, only in Australia, do you get a fire danger rating higher than extreme - "Code Red", which means "If you're in an at risk area, don't be there on this day".

    Anyway, ran a few errands and caught up with an old IRC friend this morning, just had lunch and will head off to the fire station, to be ready for what comes. It's just after 1PM, and the official temperature is around 41C (106F).

    Hoping it'll amount to nothing more than an afternoon in airconditioned comfort waiting for nothing, but one has to be ready.
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)
  • From apam@21:1/125 to Vk3jed on Fri Jan 4 17:27:06 2019
    Hoping it'll amount to nothing more than an afternoon in
    airconditioned comfort waiting for nothing, but one has to be ready.

    Hope it's a dull day for you, but best of luck if it's not.

    Andrew

    --- MagickaBBS v0.12alpha (Linux/x86_64)
    * Origin: The Fat Sandwich - sandwich.hopto.org:2023 (21:1/125)
  • From Avon@21:1/101 to apam on Fri Jan 4 21:35:38 2019
    Hi Andrew

    I'm trying to install samba on my Pi

    I hit errors even after running a full update and upgrade of the os using
    sudo apt-get update and sudo apt-get upgrade

    the errors say this after I try to install samba


    Setting up samba (2:4.5.12+dfsg-2+deb9u4) ...

    Samba is not being run as an AD Domain Controller, masking
    samba-ad-dc-service.
    Please ignore the following error about deb-systemd-helper not finding samba-ad-dc-service.
    Created symlink /etc/systemd/system/multi-user.target.wants/nmbd.service
    - /lib/systemd/system/nmbd.service.

    Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is masked.
    /usr/bin/deb-systemd-helper: error: systemctl preset failed on samba-ad-dc.service: No such file or directory Created symlink /etc/systemd/system/multi-user.target.wants/smbd.service - / lib/systemd/system/smbd.service.
    Job for smbd.service failed because a fatal signal was delivered causing the control process to dump core.
    See "systemctl status smbd.service" and "journalctl -xe" for details. invoke-rc.d: initscript smbd, action "start" failed.
    ? smbd.service - Samba SMB Daemon
    Loaded: loaded (/lib/systemd/system/smbd.service; enabled; vendor preset: enabled)
    Active: failed (Result: core-dump) since Fri 2019-01-04 16:29:04 NZDT;
    100ms ago
    Docs: man:smbd(8)
    man:samba(7)
    man:smb.conf(5)
    Process: 2807 ExecStart=/usr/sbin/smbd $SMBDOPTIONS (code=dumped, signal=SEGV)
    Main PID: 2807 (code=dumped, signal=SEGV)

    Jan 04 16:29:03 raspberrypi systemd[1]: Starting Samba SMB Daemon...
    Jan 04 16:29:04 raspberrypi systemd[1]: smbd.service: Main process exited, c.EGV
    Jan 04 16:29:04 raspberrypi systemd[1]: Failed to start Samba SMB Daemon.
    Jan 04 16:29:04 raspberrypi systemd[1]: smbd.service: Unit entered failed state.
    Jan 04 16:29:04 raspberrypi systemd[1]: smbd.service: Failed with result 'co.p'.
    Hint: Some lines were ellipsized, use -l to show in full.
    dpkg: error processing package samba (--configure):
    subprocess installed post-installation script returned error exit status 1 Setting up samba-dsdb-modules (2:4.5.12+dfsg-2+deb9u4) ...
    Setting up attr (1:2.4.47-2) ...
    Setting up samba-vfs-modules (2:4.5.12+dfsg-2+deb9u4) ...
    Processing triggers for libc-bin (2.24-11+deb9u3) ...
    Processing triggers for systemd (232-25+deb9u6) ...
    Errors were encountered while processing:
    samba
    E: Sub-process /usr/bin/dpkg returned an error code (1)




    any ideas on how to fix this? I;m not sure, I did try to remove samba and reinstall but it still borks... it's weird :(


    ──────────────────────────────────────── ──── E∙avon@bbs.nz ────── W∙bbs.nz ─── ──── K∙keybase.io/avon ──────────────

    --- Mystic BBS v1.12 A42 2018/12/30 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Vk3jed@21:1/109 to apam on Fri Jan 4 19:19:00 2019
    On 01-04-19 12:27, apam wrote to Vk3jed <=-

    Hope it's a dull day for you, but best of luck if it's not.

    Yep. Just arrived, bit cooler than home inside. :) So far, all is quiet *touch wood*


    ... Lymph (v.), to walk with a lisp.
    === MultiMail/Linux v0.51
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)
  • From apam@21:1/125 to Avon on Fri Jan 4 23:32:16 2019
    any ideas on how to fix this? I;m not sure, I did try to remove samba
    and reinstall but it still borks... it's weird :(

    I don't know sorry.

    Andrew

    --- MagickaBBS v0.12alpha (Linux/x86_64)
    * Origin: The Fat Sandwich - sandwich.hopto.org:2023 (21:1/125)
  • From deon@21:2/116.1 to Avon on Fri Jan 4 15:26:40 2019
    On 01/04/19, Avon said the following...
    Main PID: 2807 (code=dumped, signal=SEGV)

    Hmm... this is not good. This is where strace sometimes helps, and if you can play with gdb - you can analyze the coredump and see where in the code it segfaults.

    Those dumps sometimes give you a clue of what the app is doing (or trying to do) - which gives a tip of where to look (eg: could be as simple as a bad config file...)

    ...deon

    _--_|\ | Deon George
    / \ | Chinwag BBS - A BBS on a PI in Docker!
    \_.__.*/ |
    V | Coming from the 'burbs of Melbourne, Australia

    --- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
    * Origin: Chinwag | MysticBBS in Docker on a Pi! (21:2/116.1)
  • From Pequito@21:1/126 to Avon on Fri Jan 4 10:53:06 2019
    On 04 Jan 2019, Avon said the following...

    Hi Andrew

    I'm trying to install samba on my Pi

    I hit errors even after running a full update and upgrade of the os
    using sudo apt-get update and sudo apt-get upgrade

    Avon,

    What is the command you are using to install samba might make all the difference.

    aka: sudo apt install samba samba-common-bin

    Cheers!

    |08+--- |07- |15-∙
    |08: |15pequito |08<|07<|14.|11PH|15EN|11OM|14.|07>|08>
    |08: |02telnet://|10twinklebbs.net
    |08+--- |07- |15-∙

    --- Mystic BBS v1.12 A42 2018/12/30 (Linux/64)
    * Origin: Twinkle BBS # (21:1/126)
  • From Avon@21:1/101 to Pequito on Sat Jan 5 15:39:00 2019
    On 04 Jan 2019, Pequito pondered and said...

    What is the command you are using to install samba might make all the difference.
    aka: sudo apt install samba samba-common-bin

    I did use that as it was given as the example on the RPi wiki/website but I recall the system said the samba-common-bin was already installed... so
    perhaps that's it?

    I then did this

    [snip]

    pi@raspberrypi:~ $ sudo apt-get remove samba
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    The following packages were automatically installed and are no longer
    required:
    attr libaio1 python-dnspython samba-dsdb-modules samba-vfs-modules tdb-tools Use 'sudo apt autoremove' to remove them.
    The following packages will be REMOVED:
    samba
    0 upgraded, 0 newly installed, 1 to remove and 156 not upgraded.
    1 not fully installed or removed.
    After this operation, 11.0 MB disk space will be freed.
    Do you want to continue? [Y/n] y
    (Reading database ... 137672 files and directories currently installed.) Removing samba (2:4.5.12+dfsg-2+deb9u4) ...
    Processing triggers for libc-bin (2.24-11+deb9u3) ...
    Processing triggers for man-db (2.7.6.1-2) ...
    pi@raspberrypi:~ $ sudo apt-get remove samba-common-bin
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    The following packages were automatically installed and are no longer
    required:
    attr libaio1 python-crypto python-dnspython python-ldb python-samba
    python-tdb samba-dsdb-modules samba-vfs-modules tdb-tools
    Use 'sudo apt autoremove' to remove them.
    The following packages will be REMOVED:
    samba-common-bin
    0 upgraded, 0 newly installed, 1 to remove and 156 not upgraded.
    After this operation, 1,339 kB disk space will be freed.
    Do you want to continue? [Y/n] y
    (Reading database ... 137482 files and directories currently installed.) Removing samba-common-bin (2:4.5.12+dfsg-2+deb9u4) ...
    Processing triggers for man-db (2.7.6.1-2) ...
    pi@raspberrypi:~ $ sudo apt-get remove samba-common-bin
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    Package 'samba-common-bin' is not installed, so not removed
    The following packages were automatically installed and are no longer
    required:
    attr libaio1 python-crypto python-dnspython python-ldb python-samba
    python-tdb samba-dsdb-modules samba-vfs-modules tdb-tools
    Use 'sudo apt autoremove' to remove them.
    0 upgraded, 0 newly installed, 0 to remove and 156 not upgraded. pi@raspberrypi:~ $ sudo apt autoremove
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    The following packages will be REMOVED:
    attr libaio1 python-crypto python-dnspython python-ldb python-samba
    python-tdb samba-dsdb-modules samba-vfs-modules tdb-tools
    0 upgraded, 0 newly installed, 10 to remove and 156 not upgraded.
    After this operation, 12.6 MB disk space will be freed.
    Do you want to continue? [Y/n]
    (Reading database ... 137454 files and directories currently installed.) Removing attr (1:2.4.47-2) ...
    Removing samba-vfs-modules (2:4.5.12+dfsg-2+deb9u4) ...
    Removing libaio1:armhf (0.3.110-3) ...
    Removing python-samba (2:4.5.12+dfsg-2+deb9u4) ...
    Removing python-crypto (2.6.1-7) ...
    Removing python-dnspython (1.15.0-1) ...
    Removing python-ldb (2:1.1.27-1) ...
    Removing python-tdb (1.3.11-2) ...
    Removing samba-dsdb-modules (2:4.5.12+dfsg-2+deb9u4) ...
    Removing tdb-tools (1.3.11-2) ...
    Processing triggers for libc-bin (2.24-11+deb9u3) ...
    Processing triggers for man-db (2.7.6.1-2) ...
    pi@raspberrypi:~ $

    [snip]

    Not sure if I should reboot first (but I didn't) then I ran

    sudo apt-get install samba samba-common-bin

    [snip]

    pi@raspberrypi:~ $ sudo apt-get install samba samba-common-bin
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    The following additional packages will be installed:
    attr libaio1 python-crypto python-dnspython python-ldb python-samba
    python-tdb samba-dsdb-modules samba-vfs-modules tdb-tools
    Suggested packages:
    python-crypto-dbg python-crypto-doc python-gpgme bind9 bind9utils ctdb
    ldb-tools smbldap-tools winbind ufw heimdal-clients
    The following NEW packages will be installed:
    attr libaio1 python-crypto python-dnspython python-ldb python-samba
    python-tdb samba samba-common-bin samba-dsdb-modules samba-vfs-modules
    tdb-tools
    0 upgraded, 12 newly installed, 0 to remove and 156 not upgraded.
    Need to get 0 B/3,683 kB of archives.
    After this operation, 24.9 MB of additional disk space will be used.
    Do you want to continue? [Y/n]
    Selecting previously unselected package python-dnspython.
    (Reading database ... 136772 files and directories currently installed.) Preparing to unpack .../00-python-dnspython_1.15.0-1_all.deb ...
    Unpacking python-dnspython (1.15.0-1) ...
    Selecting previously unselected package python-crypto.
    Preparing to unpack .../01-python-crypto_2.6.1-7_armhf.deb ...
    Unpacking python-crypto (2.6.1-7) ...
    Selecting previously unselected package python-ldb.
    Preparing to unpack .../02-python-ldb_2%3a1.1.27-1_armhf.deb ...
    Unpacking python-ldb (2:1.1.27-1) ...
    Selecting previously unselected package python-tdb.
    Preparing to unpack .../03-python-tdb_1.3.11-2_armhf.deb ...
    Unpacking python-tdb (1.3.11-2) ...
    Selecting previously unselected package python-samba.
    Preparing to unpack .../04-python-samba_2%3a4.5.12+dfsg-2+deb9u4_armhf.deb ... Unpacking python-samba (2:4.5.12+dfsg-2+deb9u4) ...
    Selecting previously unselected package samba-common-bin.
    Preparing to unpack
    .../05-samba-common-bin_2%3a4.5.12+dfsg-2+deb9u4_armhf.deb ...
    Unpacking samba-common-bin (2:4.5.12+dfsg-2+deb9u4) ...
    Selecting previously unselected package tdb-tools.
    Preparing to unpack .../06-tdb-tools_1.3.11-2_armhf.deb ...
    Unpacking tdb-tools (1.3.11-2) ...
    Selecting previously unselected package samba.
    Preparing to unpack .../07-samba_2%3a4.5.12+dfsg-2+deb9u4_armhf.deb ... Unpacking samba (2:4.5.12+dfsg-2+deb9u4) ...
    Selecting previously unselected package attr.
    Preparing to unpack .../08-attr_1%3a2.4.47-2_armhf.deb ...
    Unpacking attr (1:2.4.47-2) ...
    Selecting previously unselected package libaio1:armhf.
    Preparing to unpack .../09-libaio1_0.3.110-3_armhf.deb ...
    Unpacking libaio1:armhf (0.3.110-3) ...
    Selecting previously unselected package samba-dsdb-modules.
    Preparing to unpack .../10-samba-dsdb-modules_2%3a4.5.12+dfsg-2+deb9u4_armhf.deb ...
    Unpacking samba-dsdb-modules (2:4.5.12+dfsg-2+deb9u4) ...
    Selecting previously unselected package samba-vfs-modules.
    Preparing to unpack
    .../11-samba-vfs-modules_2%3a4.5.12+dfsg-2+deb9u4_armhf.deb ...
    Unpacking samba-vfs-modules (2:4.5.12+dfsg-2+deb9u4) ...
    Setting up python-dnspython (1.15.0-1) ...
    Setting up python-crypto (2.6.1-7) ...
    Setting up python-tdb (1.3.11-2) ...
    Processing triggers for libc-bin (2.24-11+deb9u3) ...
    Setting up libaio1:armhf (0.3.110-3) ...
    Processing triggers for systemd (232-25+deb9u6) ...
    Setting up tdb-tools (1.3.11-2) ...
    update-alternatives: using /usr/bin/tdbbackup.tdbtools to provide /usr/bin/tdbbackup (tdbbackup) in auto mode
    Processing triggers for man-db (2.7.6.1-2) ...
    Setting up samba-dsdb-modules (2:4.5.12+dfsg-2+deb9u4) ...
    Setting up attr (1:2.4.47-2) ...
    Setting up python-ldb (2:1.1.27-1) ...
    Setting up samba-vfs-modules (2:4.5.12+dfsg-2+deb9u4) ...
    Setting up python-samba (2:4.5.12+dfsg-2+deb9u4) ...
    Setting up samba-common-bin (2:4.5.12+dfsg-2+deb9u4) ...
    Setting up samba (2:4.5.12+dfsg-2+deb9u4) ...
    Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is masked.
    /usr/bin/deb-systemd-helper: error: systemctl preset failed on samba-ad-dc.service: No such file or directory

    Job for smbd.service failed because a fatal signal was delivered causing the control process to dump core.
    See "systemctl status smbd.service" and "journalctl -xe" for details. invoke-rc.d: initscript smbd, action "start" failed.
    ? smbd.service - Samba SMB Daemon
    Loaded: loaded (/lib/systemd/system/smbd.service; enabled; vendor preset: enabled)
    Active: failed (Result: core-dump) since Sat 2019-01-05 10:36:49 NZDT;
    128ms ago
    Docs: man:smbd(8)
    man:samba(7)
    man:smb.conf(5)
    Process: 13498 ExecStart=/usr/sbin/smbd $SMBDOPTIONS (code=dumped, signal=SEGV)
    Main PID: 13498 (code=dumped, signal=SEGV)

    Jan 05 10:36:48 raspberrypi systemd[1]: Starting Samba SMB Daemon...
    Jan 05 10:36:49 raspberrypi systemd[1]: smbd.service: Main process exited, c.EGV
    Jan 05 10:36:49 raspberrypi systemd[1]: Failed to start Samba SMB Daemon.
    Jan 05 10:36:49 raspberrypi systemd[1]: smbd.service: Unit entered failed state.
    Jan 05 10:36:49 raspberrypi systemd[1]: smbd.service: Failed with result 'co.p'.
    Hint: Some lines were ellipsized, use -l to show in full.
    dpkg: error processing package samba (--configure):
    subprocess installed post-installation script returned error exit status 1 Processing triggers for libc-bin (2.24-11+deb9u3) ...
    Errors were encountered while processing:
    samba
    E: Sub-process /usr/bin/dpkg returned an error code (1)

    [snip]

    So yeah, seems it does not like to install :(


    ──────────────────────────────────────── ──── E∙avon@bbs.nz ────── W∙bbs.nz ─── ──── K∙keybase.io/avon ──────────────

    --- Mystic BBS v1.12 A42 2018/12/30 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to deon on Sat Jan 5 15:39:38 2019
    On 04 Jan 2019, deon pondered and said...

    Hmm... this is not good. This is where strace sometimes helps, and if
    you can play with gdb - you can analyze the coredump and see where in
    the code it segfaults.

    Those dumps sometimes give you a clue of what the app is doing (or
    trying to do) - which gives a tip of where to look (eg: could be as
    simple as a bad config file...)

    Those are tools and steps a bit beyond this simple linux man I'm afraid to
    say :) But thanks for the feedback :)


    ──────────────────────────────────────── ──── E∙avon@bbs.nz ────── W∙bbs.nz ─── ──── K∙keybase.io/avon ──────────────

    --- Mystic BBS v1.12 A42 2018/12/30 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Pequito@21:1/126 to Avon on Fri Jan 4 20:00:15 2019
    On 05 Jan 2019, Avon said the following...

    I will not quote all of that so will just outline what should be done to see
    if this helps correct the issue:

    sudo apt remove samba
    sudo apt autoremove
    sudo apt update
    sudo reboot
    sudo apt install samba samba-common-bin

    Cheers!

    |08+--- |07- |15-∙
    |08: |15pequito |08<|07<|14.|11PH|15EN|11OM|14.|07>|08>
    |08: |02telnet://|10twinklebbs.net
    |08+--- |07- |15-∙

    --- Mystic BBS v1.12 A42 2018/12/30 (Linux/64)
    * Origin: Twinkle BBS # (21:1/126)
  • From Blue White@21:4/134 to Vk3jed on Fri Jan 4 23:59:16 2019
    Vk3jed wrote to All <=-

    Well, the weather gods have pulled out a shocker for us here today. Forecast top of 45C (113F), winds 40 km/h (35 mph) gusting to 65 km/h
    (41 mph), RH 9%, with an unstable atmosphere and a late change.

    Is the area you are in a desert area? Reason I ask is that, when it gets anywhere over 90F here, the RH is rarely < 50%. As a result, our heat
    indices can get into the one-teens F, but the actual temperature rarely does.


    ... Computer Hacker wanted. Must have own axe.
    --- MultiMail
    * Origin: Possum Lodge South * possumso.fsxnet.nz:7636/SSH:2122 (21:4/134)
  • From Vk3jed@21:1/109 to Blue White on Sun Jan 6 13:41:00 2019
    On 01-04-19 18:59, Blue White wrote to Vk3jed <=-

    Vk3jed wrote to All <=-

    Well, the weather gods have pulled out a shocker for us here today. Forecast top of 45C (113F), winds 40 km/h (35 mph) gusting to 65 km/h
    (41 mph), RH 9%, with an unstable atmosphere and a late change.

    Is the area you are in a desert area? Reason I ask is that, when it
    gets anywhere over 90F here, the RH is rarely < 50%. As a result, our heat indices can get into the one-teens F, but the actual temperature rarely does.

    It's officially "temperate", but actualy not far off being semi arid. Humidity does tend to drop on the hottest days, because the winds come off the central deserts. Friday bottomed out at around 9% humidity. The problem here is 110+F/9% with wind is prime fire conditions. Fortunately, it was a very quiet day in our patch of the state. Only one call in a neighbouring area for a false alarm - a "smoke sighting" that turned out to be raised dust. We weren't called to that one.


    ... Crayons can take you more places than starships. * Guinan
    === MultiMail/Win v0.51
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)
  • From Avon@21:1/101 to Pequito on Sun Jan 6 19:47:08 2019
    On 04 Jan 2019, Pequito pondered and said...

    sudo apt remove samba
    sudo apt autoremove
    sudo apt update
    sudo reboot
    sudo apt install samba samba-common-bin

    Thanks for the suggestions. Sadly the final command failed again. Stuffed if
    I know why it fails when on paper you would think it should just install.

    [snip]

    Setting up samba (2:4.5.12+dfsg-2+deb9u4) ...
    Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is masked.
    /usr/bin/deb-systemd-helper: error: systemctl preset failed on samba-ad-dc.service: No such file or directory Job for smbd.service failed because a fatal signal was delivered causing the
    control process to dump core.
    See "systemctl status smbd.service" and "journalctl -xe" for details. invoke-rc.d: initscript smbd, action "start" failed.
    ? smbd.service - Samba SMB Daemon
    Loaded: loaded (/lib/systemd/system/smbd.service; enabled; vendor preset: enabled)
    Active: failed (Result: core-dump) since Sun 2019-01-06 14:44:00 NZDT;
    104ms ago
    Docs: man:smbd(8)
    man:samba(7)
    man:smb.conf(5)
    Process: 2844 ExecStart=/usr/sbin/smbd $SMBDOPTIONS (code=dumped, signal=SEGV)
    Main PID: 2844 (code=dumped, signal=SEGV)

    Jan 06 14:43:59 raspberrypi systemd[1]: Starting Samba SMB Daemon...
    Jan 06 14:44:00 raspberrypi systemd[1]: smbd.service: Main process exited, c.EGV
    Jan 06 14:44:00 raspberrypi systemd[1]: Failed to start Samba SMB Daemon.
    Jan 06 14:44:00 raspberrypi systemd[1]: smbd.service: Unit entered failed state.
    Jan 06 14:44:00 raspberrypi systemd[1]: smbd.service: Failed with result 'co.p'.
    Hint: Some lines were ellipsized, use -l to show in full.
    dpkg: error processing package samba (--configure):
    subprocess installed post-installation script returned error exit status 1 Setting up samba-dsdb-modules (2:4.5.12+dfsg-2+deb9u4) ...
    Setting up attr (1:2.4.47-2) ...
    Setting up samba-vfs-modules (2:4.5.12+dfsg-2+deb9u4) ...
    Processing triggers for libc-bin (2.24-11+deb9u3) ...
    Errors were encountered while processing:
    samba
    E: Sub-process /usr/bin/dpkg returned an error code (1)

    [snip]

    Best, Paul


    ──────────────────────────────────────── ──── E∙avon@bbs.nz ────── W∙bbs.nz ─── ──── K∙keybase.io/avon ──────────────

    --- Mystic BBS v1.12 A42 2018/12/30 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From esc@21:1/112 to Pequito on Sun Jan 6 11:46:04 2019
    I will not quote all of that so will just outline what should be done to see if this helps correct the issue:

    sudo apt remove samba

    ... <snip> ...
    One thing I'd recommend after fully removing something is `sudo apt purge <package>` to get rid of all the cruft and local configuration and stuff.

    --- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
    * Origin: Black Flag <ACiD Telnet HQ> blackflagbbs.com (21:1/112)
  • From Avon@21:1/101 to esc on Mon Jan 7 14:37:16 2019
    On 06 Jan 2019, esc pondered and said...

    One thing I'd recommend after fully removing something is `sudo apt purge <package>` to get rid of all the cruft and local configuration and stuff.

    I'll try that also - thanks!


    ──── E∙avon@bbs.nz ────── W∙bbs.nz ─── ──── K∙keybase.io/avon ──────────────

    --- Mystic BBS v1.12 A42 2018/12/30 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to esc on Mon Jan 7 20:49:04 2019
    On 06 Jan 2019, esc pondered and said...

    One thing I'd recommend after fully removing something is `sudo apt purge <package>` to get rid of all the cruft and local configuration and stuff.

    I think that did the trick - thanks :)

    I'll keep testing to see if I can set things up further now.

    [snip]

    pi@raspberrypi:~ $ sudo apt install samba samba-common-bin
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    The following additional packages will be installed:
    attr libaio1 python-dnspython python-ldb python-samba python-tdb
    samba-dsdb-modules samba-vfs-modules tdb-tools
    Suggested packages:
    python-gpgme bind9 bind9utils ctdb ldb-tools smbldap-tools winbind ufw
    heimdal-clients
    The following NEW packages will be installed:
    attr libaio1 python-dnspython python-ldb python-samba python-tdb samba
    samba-common-bin samba-dsdb-modules samba-vfs-modules tdb-tools
    0 upgraded, 11 newly installed, 0 to remove and 40 not upgraded.
    Need to get 0 B/3,431 kB of archives.
    After this operation, 23.5 MB of additional disk space will be used.
    Do you want to continue? [Y/n]
    Selecting previously unselected package python-dnspython.
    (Reading database ... 165793 files and directories currently installed.) Preparing to unpack .../00-python-dnspython_1.15.0-1_all.deb ...
    Unpacking python-dnspython (1.15.0-1) ...
    Selecting previously unselected package python-ldb.
    Preparing to unpack .../01-python-ldb_2%3a1.1.27-1_armhf.deb ...
    Unpacking python-ldb (2:1.1.27-1) ...
    Selecting previously unselected package python-tdb.
    Preparing to unpack .../02-python-tdb_1.3.11-2_armhf.deb ...
    Unpacking python-tdb (1.3.11-2) ...
    Selecting previously unselected package python-samba.
    Preparing to unpack .../03-python-samba_2%3a4.5.12+dfsg-2+deb9u4_armhf.deb ... Unpacking python-samba (2:4.5.12+dfsg-2+deb9u4) ...
    Selecting previously unselected package samba-common-bin.
    Preparing to unpack
    .../04-samba-common-bin_2%3a4.5.12+dfsg-2+deb9u4_armhf.deb ...
    Unpacking samba-common-bin (2:4.5.12+dfsg-2+deb9u4) ...
    Selecting previously unselected package tdb-tools.
    Preparing to unpack .../05-tdb-tools_1.3.11-2_armhf.deb ...
    Unpacking tdb-tools (1.3.11-2) ...
    Selecting previously unselected package samba.
    Preparing to unpack .../06-samba_2%3a4.5.12+dfsg-2+deb9u4_armhf.deb ... Unpacking samba (2:4.5.12+dfsg-2+deb9u4) ...
    Selecting previously unselected package attr.
    Preparing to unpack .../07-attr_1%3a2.4.47-2_armhf.deb ...
    Unpacking attr (1:2.4.47-2) ...
    Selecting previously unselected package libaio1:armhf.
    Preparing to unpack .../08-libaio1_0.3.110-3_armhf.deb ...
    Unpacking libaio1:armhf (0.3.110-3) ...
    Selecting previously unselected package samba-dsdb-modules.
    Preparing to unpack .../09-samba-dsdb-modules_2%3a4.5.12+dfsg-2+deb9u4_armhf.deb ...
    Unpacking samba-dsdb-modules (2:4.5.12+dfsg-2+deb9u4) ...
    Selecting previously unselected package samba-vfs-modules.
    Preparing to unpack
    .../10-samba-vfs-modules_2%3a4.5.12+dfsg-2+deb9u4_armhf.deb ...
    Unpacking samba-vfs-modules (2:4.5.12+dfsg-2+deb9u4) ...
    Setting up python-dnspython (1.15.0-1) ...
    Setting up python-tdb (1.3.11-2) ...
    Processing triggers for libc-bin (2.24-11+deb9u3) ...
    Setting up libaio1:armhf (0.3.110-3) ...
    Processing triggers for systemd (232-25+deb9u6) ...
    Setting up tdb-tools (1.3.11-2) ...
    update-alternatives: using /usr/bin/tdbbackup.tdbtools to provide /usr/bin/tdbbackup (tdbbackup) in auto mode
    Processing triggers for man-db (2.7.6.1-2) ...
    Setting up samba-dsdb-modules (2:4.5.12+dfsg-2+deb9u4) ...
    Setting up attr (1:2.4.47-2) ...
    Setting up python-ldb (2:1.1.27-1) ...
    Setting up samba-vfs-modules (2:4.5.12+dfsg-2+deb9u4) ...
    Setting up python-samba (2:4.5.12+dfsg-2+deb9u4) ...
    Setting up samba-common-bin (2:4.5.12+dfsg-2+deb9u4) ...
    Setting up samba (2:4.5.12+dfsg-2+deb9u4) ...
    Samba is not being run as an AD Domain Controller, masking
    samba-ad-dc-service.
    Please ignore the following error about deb-systemd-helper not finding samba-ad-dc-service.
    Created symlink /etc/systemd/system/multi-user.target.wants/nmbd.service /lib/systemd/system/nmbd.service. Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is masked.

    /usr/bin/deb-systemd-helper: error: systemctl preset failed on samba-ad-dc.service: No such file or directory Created symlink /etc/systemd/system/multi-user.target.wants/smbd.service /lib/systemd/system/smbd.service. Processing triggers for libc-bin (2.24-11+deb9u3) ...
    Processing triggers for systemd (232-25+deb9u6) ...

    [snip]

    Best, Paul


    ──── E∙avon@bbs.nz ────── W∙bbs.nz ─── ──── K∙keybase.io/avon ──────────────

    --- Mystic BBS v1.12 A42 2018/12/30 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From nathanael@21:4/123 to deon on Sat Jan 26 23:35:23 2019
    Hey, I'm not terribly familiar with Docker, but I've got it installed on both my NAS and my Pi. I've pulled your Mystic Docker image and launched a container. Now how the bloody hell do I connect to it? telnetting to port 23
    on my NAS doesn't do it.

    +=====================+-+=======+----------------------------------------
    | *H:U:M:O:N:G:O:U:S* | | B:B:S | nathanael : jenandcal.familyds.org:2323 +=====================+-+=======+----------------------------------------

    --- Mystic BBS v1.12 A41 2018/12/27 (Raspberry Pi/32)
    * Origin: *HUMONGOUS* BBS (21:4/123)
  • From Deon George@21:2/116 to nathanael on Sun Jan 27 04:34:16 2019
    Howdy,
    26 Jan 19 18:35, you wrote to deon:

    Hey, I'm not terribly familiar with Docker, but I've got it installed
    on both my NAS and my Pi. I've pulled your Mystic Docker image and launched a container. Now how the bloody hell do I connect to it? telnetting to port 23 on my NAS doesn't do it.

    Awesome :) BTW: I'll update it soon to the latest A42 or so - I have too many things on my plate at the moment :)

    Just realised my blog was missing an important step, so I'll update it, but basically you need to add "-p X:Y" where X is the host port, can be anything want it to be (I use 10023), and Y is port 23 inside the container (since that is what I've configured Mystic to listen on).

    If you want to use BINKP and SSH, add more "-p" options, with them porting to 24554 and port 22 respectively. (All pre-req's are installed, so it should just run.)

    For example, my mystic starts with "-p 10023:23 -p 24554:24554 -p 10022:22 -v /srv/docker/chinwag-mbbs/data:/mystic/data"

    (If you want to start a second one - make sure the -p ports are -v volumes are set appropriately for the second instance (different to the first), etc.

    Yell out if you still get stuck.

    ...deon

    --- GoldED+/LNX 1.1.5--b20180707
    * Origin: Chinwag | MBSE in Docker on Pi (21:2/116)
  • From Deon George@21:2/116 to nathanael on Sun Jan 27 04:45:03 2019
    26 Jan 19 23:34, I wrote to you:

    For example, my mystic starts with "-p 10023:23 -p 24554:24554 -p
    10022:22 -v /srv/docker/chinwag-mbbs/data:/mystic/data"

    Yell out if you still get stuck.

    Shoot, hit send too quickly.

    Also, when you want to run the mystic utilities (like setup your sysop account and give it privilges, as well as setup networks, etc), you'll want to do "docker exec -it <CONTAINER ID> ./mystic -cfg" (where container ID is the id of the container when you start it - you can always see it by typing "docker ps"). If you were running mutil it would be "docker exec -it <CONTAINER ID> ./mutil ...", etc

    If you want to get onto the console you can "docker attach <CONTAINER ID>" and you'll be on the console (so you can shutdown the server for example, or see the status) - press a key to refresh the screen, since it will most likely be blank at first. To "detach" you need to press CTRL-P CTRL-Q.

    ...deon

    --- GoldED+/LNX 1.1.5--b20180707
    * Origin: Chinwag | MBSE in Docker on Pi (21:2/116)
  • From nathanael@21:4/123 to Deon George on Mon Jan 28 15:35:42 2019
    Thanks -- all very useful commands. And I figured out the one I really
    needed: "docker exec -it <CONTAINER_ID> bash".

    So I've got a Mystic docker container up and running on my Synology NAS and
    am able to connect to it and telnet in. I've also set up drive mappings for persistence, which leads to a question:

    In your examples, you have only mapped a local dir to /mystic/data. But for persistence across containers or restarts, I guess I'll have to map at least /mystic/menus and /mystic/doors as well.

    So what drive mappings do you maintain on your production images?

    I'm heading out to the US tomorrow, so I probably won't have time to continue playing with Docker/Mystic until I get back in a couple of weeks.

    +=====================+-+=======+----------------------------------------
    | *H:U:M:O:N:G:O:U:S* | | B:B:S | nathanael : jenandcal.familyds.org:2323 +=====================+-+=======+----------------------------------------

    --- Mystic BBS v1.12 A41 2018/12/27 (Raspberry Pi/32)
    * Origin: *HUMONGOUS* BBS (21:4/123)
  • From deon@21:2/116.1 to nathanael on Mon Jan 28 09:19:44 2019
    On 01/28/19, nathanael said the following...
    In your examples, you have only mapped a local dir to /mystic/data. But for persistence across containers or restarts, I guess I'll have to map
    at least /mystic/menus and /mystic/doors as well.

    No - you put everything on /mystic/data/... and it will persist, if you may
    -v to your host. (Actually it will persist on a dynamic docker volume if you dont use "-v" - as long as you dont do docker rm -v <CONTAINERID>. In the latter case, you need to use the --volumes-from <CONTAINERID> if you want to replace the original container.)

    When you first start the container, it should a default setup inside /mystic/data, and you can see that I have changed the config so that
    everything is /mystic/data/<SOMETHING>...

    I'm heading out to the US tomorrow, so I probably won't have time to continue playing with Docker/Mystic until I get back in a couple of
    weeks.

    Enjoy your trip :)

    ...deon

    _--_|\ | Deon George
    / \ | Chinwag BBS - A BBS on a PI in Docker!
    \_.__.*/ |
    V | Coming from the 'burbs of Melbourne, Australia

    --- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
    * Origin: Chinwag | MysticBBS in Docker on a Pi! (21:2/116.1)
  • From nathanael@21:4/123 to deon on Mon Jan 28 18:13:43 2019
    /mystic/data, and you can see that I have changed the config so that everything is /mystic/data/<SOMETHING>...

    Ah, gotcha. So when you've updated the image to A41-ish I just pull it and do a --volumes-from ?

    Enjoy your trip :)

    Hope to, though it's unusually cold there ATM, even by Wisconsin standards. Thought about taking my daughter skiing -- she's never been. But -25C
    isn't ideal for downhill -- the snow runs a bit too fast and control is more difficult. -5C is closer to ideal for beginners.

    Cross-country, ice skating and ice fishing are still possibilities, though,
    and maybe a bit of curling. And of course snowmen, snowball fights, snow shoveling...

    +=====================+-+=======+----------------------------------------
    | *H:U:M:O:N:G:O:U:S* | | B:B:S | nathanael : jenandcal.familyds.org:2323 +=====================+-+=======+----------------------------------------

    --- Mystic BBS v1.12 A41 2018/12/27 (Raspberry Pi/32)
    * Origin: *HUMONGOUS* BBS (21:4/123)
  • From deon@21:2/116.1 to nathanael on Mon Jan 28 16:16:27 2019
    On 01/28/19, nathanael said the following...
    Ah, gotcha. So when you've updated the image to A41-ish I just pull it
    and do a --volumes-from ?

    Yes, if you are not using "-v". Otherwise you would just start it the same
    way (with the -v)...

    But -25C isn't ideal for downhill -- the snow runs a bit too fast and control is more difficult. -5C is closer to ideal for beginners.

    Yeah, I've done the -25C skiing (long time ago in Whistler, before Whistler became really popular). Its cold :)

    though, and maybe a bit of curling. And of course snowmen, snowball fights, snow shoveling...

    That's the best part with kids... :)

    ...deon

    _--_|\ | Deon George
    / \ | Chinwag BBS - A BBS on a PI in Docker!
    \_.__.*/ |
    V | Coming from the 'burbs of Melbourne, Australia

    --- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
    * Origin: Chinwag | MysticBBS in Docker on a Pi! (21:2/116.1)
  • From Avon@21:1/101 to All on Sun Oct 6 14:30:03 2019
    I think I have made progress on my first hurdle.
    With samba running on the Deb 10 box I set up the following share

    comment = Public Folder
    path =/home/bbs/Public
    read only = no
    guest ok = yes
    browseable = yes
    force group = bbs
    force user = bbs


    This seems to do the tick so that I can now copy files from the windows box
    to the linux box and they can then be moved off to other parts of the new
    file system.

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From tallship@21:2/104 to Avon on Sat Oct 5 20:48:00 2019
    On 06 Oct 2019, Avon said the following...

    I think I have made progress on my first hurdle.
    With samba running on the Deb 10 box I set up the following share

    comment = Public Folder
    path =/home/bbs/Public
    read only = no
    guest ok = yes
    browseable = yes
    force group = bbs
    force user = bbs


    This seems to do the tick so that I can now copy files from the windows box to the linux box and they can then be moved off to other parts of
    the new file system.


    Hip Hip... Hooray!

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
    * Origin: Vger.Cloud - NOMAD Internetwork (21:2/104)
  • From Avon@21:1/101 to tallship on Sun Oct 6 17:13:28 2019
    On 05 Oct 2019 at 04:48p, tallship pondered and said...



    Hip Hip... Hooray!

    I'm halfway to the start line now, just gotta sort some VNC access so I can
    run the box headless but have a comfortable GUI experience to start with.

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From tallship@21:2/104 to Avon on Sat Oct 5 21:41:24 2019
    On 06 Oct 2019, Avon said the following...

    I'm halfway to the start line now, just gotta sort some VNC access so I can run the box headless but have a comfortable GUI experience to start with.


    That is totally fricken' awesome broham!

    Welcome BACK, from the darkside, "Luke" ;)

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
    * Origin: Vger.Cloud - NOMAD Internetwork (21:2/104)