MisterWolfe

Members
  • Content count

    73
  • Joined

  • Last visited

Community Reputation

0 Neutral

About MisterWolfe

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    British Columbia

Recent Profile Visitors

148 profile views
  1. MisterWolfe

    Crontab added through go script not working

    Thank you for the information. It's greatly appreciated.
  2. MisterWolfe

    Crontab added through go script not working

    Sorry to resurrect an old thread. I have been using the above method for cron jobs for a number of years successfully. On Feb 23, cron jobs stopped running that I've set up in the /boot/config/plugins/mycron folder. The cron jobs are inside a file called bkp.cron. The cron jobs in the file are all rsyncs that I use to back up primary data to a secondary location. The cron jobs stopped working around the time I moved from 6.4 to 6.5. I haven't downgraded to test if an earlier version works yet. It's a production environment and I don't want to take it offline unless I have to. Upgrading to the latest version of Unraid, 6.5.1-rc1, hasn't resolved the issue. Has anyone else experienced this? I've attached diags. luna-diagnostics-20180323-0854.zip
  3. I mounted the drive manually as part of my testing process and the drive was indeed mounted when I attempted to run docker. See image below. To confirm that not using auto mount may have been an issue, I restarted the array with auto mount enabled. I still have the same issue. As part of this, the default appdata used to let me go to the /mnt directory and choose which disk I wanted to put my appdata folder on. It now goes to the user/array folder and does not let me drill down further intro the tree. My next testing step will be to copy the docker.img and appdata folders to a different drive and see if they are recognized.
  4. Did the docker settings change in this release? After updating, my docker paths are now showing as invalid. My docker paths point to an unassigned ssd drive that I've mounted and have been using for over a year specifically for docker. The docker.img and the appdata paths reside on this drive. I've tried to reset the paths in the docker config to no avail. I can select the docker image via the docker storage location field, but it still shows as invalid. In the appdata storage location path, it won't allow me to choose the unassigned drive at all any more. The ssd is functioning. I'm currently copying the docker data to a backup location. I've included a screen shot of the error and the diagnostic files, should they be helpful Thank you. tower-diagnostics-20171116-0922.zip
  5. MisterWolfe

    [Support] Linuxserver.io - Ubooquity

    That did it, thanks!
  6. MisterWolfe

    [Support] Linuxserver.io - Ubooquity

    I notice that the docker has been updated Ubooquity version 2.1. It looks like the update made some internal changes that made the existing databases inaccessible. The databases are repopulating from the path set in the docker setup, rather than from the path set in the ubooquity admin area. The admin page is also no longer accessible via the normal url method. Is there a new method I should be using to access the admin page, and if not, how can I revert back to v 1.10? Thanks!
  7. MisterWolfe

    Call Trace warnings in syslog

    Repairing the file system on the cache drive was the solution. Thanks again!
  8. MisterWolfe

    Call Trace warnings in syslog

    Thanks, Squid! I appreciate the assistance. I'll start a file system check and go from there.
  9. MisterWolfe

    Call Trace warnings in syslog

    I've gotten a warning about Call traces in my syslog from the Fix Common problems plugin. It looks like a kernel issue, but I'm not sure what, if anything, I can do to solve it. Any input would be appreciated. I've attached the diagnostics file, and included the call trace inside the post. Thank you! Mar 13 10:04:11 Tower kernel: ------------[ cut here ]------------ Mar 13 10:04:11 Tower kernel: WARNING: CPU: 2 PID: 13689 at fs/btrfs/extent-tree.c:134 btrfs_put_block_group+0x42/0x59 Mar 13 10:04:11 Tower kernel: Modules linked in: xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod hwmon_vid pata_marvell coretemp kvm_intel kvm r8169 mii ahci libahci sata_mv i2c_i801 intel_agp i2c_smbus intel_gtt i2c_core ata_piix agpgart asus_atk0110 acpi_cpufreq [last unloaded: md_mod] Mar 13 10:04:11 Tower kernel: CPU: 2 PID: 13689 Comm: umount Not tainted 4.9.10-unRAID #1 Mar 13 10:04:11 Tower kernel: Hardware name: System manufacturer System Product Name/P5Q-PRO, BIOS 2102 02/23/2009 Mar 13 10:04:11 Tower kernel: ffffc900053ebd20 ffffffff813a353e 0000000000000000 ffffffff81968f2d Mar 13 10:04:11 Tower kernel: ffffc900053ebd60 ffffffff8104d00c 00000086053ebd00 ffff880222bb3c00 Mar 13 10:04:11 Tower kernel: ffff880222bb3ce8 ffff880222476090 ffff880222bb3c00 ffff8802224760a0 Mar 13 10:04:11 Tower kernel: Call Trace: Mar 13 10:04:11 Tower kernel: [<ffffffff813a353e>] dump_stack+0x61/0x7e Mar 13 10:04:11 Tower kernel: [<ffffffff8104d00c>] __warn+0xb8/0xd3 Mar 13 10:04:11 Tower kernel: [<ffffffff8104d0d4>] warn_slowpath_null+0x18/0x1a Mar 13 10:04:11 Tower kernel: [<ffffffff812d591a>] btrfs_put_block_group+0x42/0x59 Mar 13 10:04:11 Tower kernel: [<ffffffff812dbc2b>] btrfs_free_block_groups+0x19d/0x39b Mar 13 10:04:11 Tower kernel: [<ffffffff812eadf9>] close_ctree+0x1d4/0x2e8 Mar 13 10:04:11 Tower kernel: [<ffffffff81137d51>] ? evict_inodes+0x128/0x137 Mar 13 10:04:11 Tower kernel: [<ffffffff812c5c50>] btrfs_put_super+0x14/0x16 Mar 13 10:04:11 Tower kernel: [<ffffffff8112305b>] generic_shutdown_super+0x6a/0xeb Mar 13 10:04:11 Tower kernel: [<ffffffff811232be>] kill_anon_super+0xd/0x17 Mar 13 10:04:11 Tower kernel: [<ffffffff812c5b97>] btrfs_kill_super+0x11/0x94 Mar 13 10:04:11 Tower kernel: [<ffffffff811234b0>] deactivate_locked_super+0x3b/0x68 Mar 13 10:04:11 Tower kernel: [<ffffffff81123e34>] deactivate_super+0x39/0x3c Mar 13 10:04:11 Tower kernel: [<ffffffff8113acd2>] cleanup_mnt+0x53/0x71 Mar 13 10:04:11 Tower kernel: [<ffffffff8113ad24>] __cleanup_mnt+0xd/0xf Mar 13 10:04:11 Tower kernel: [<ffffffff81062530>] task_work_run+0x6a/0x7d Mar 13 10:04:11 Tower kernel: [<ffffffff81002b24>] exit_to_usermode_loop+0x55/0x81 Mar 13 10:04:11 Tower kernel: [<ffffffff81002c61>] syscall_return_slowpath+0x44/0x47 Mar 13 10:04:11 Tower kernel: [<ffffffff8167d344>] entry_SYSCALL_64_fastpath+0xa7/0xa9 Mar 13 10:04:11 Tower kernel: ---[ end trace 8e45affbece91bb7 ]--- Mar 13 10:04:11 Tower kernel: ------------[ cut here ]------------ Mar 13 10:04:11 Tower kernel: WARNING: CPU: 2 PID: 13689 at fs/btrfs/extent-tree.c:10045 btrfs_free_block_groups+0x37a/0x39b Mar 13 10:04:11 Tower kernel: Modules linked in: xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod hwmon_vid pata_marvell coretemp kvm_intel kvm r8169 mii ahci libahci sata_mv i2c_i801 intel_agp i2c_smbus intel_gtt i2c_core ata_piix agpgart asus_atk0110 acpi_cpufreq [last unloaded: md_mod] Mar 13 10:04:11 Tower kernel: CPU: 2 PID: 13689 Comm: umount Tainted: G W 4.9.10-unRAID #1 Mar 13 10:04:11 Tower kernel: Hardware name: System manufacturer System Product Name/P5Q-PRO, BIOS 2102 02/23/2009 Mar 13 10:04:11 Tower kernel: ffffc900053ebd38 ffffffff813a353e 0000000000000000 ffffffff81968f2d Mar 13 10:04:11 Tower kernel: ffffc900053ebd78 ffffffff8104d00c 0000273d053ebd40 ffff880222476000 Mar 13 10:04:11 Tower kernel: ffff880221e1bc88 ffff880221e1bc00 ffff880222476b30 0000000000000000 Mar 13 10:04:11 Tower kernel: Call Trace: Mar 13 10:04:11 Tower kernel: [<ffffffff813a353e>] dump_stack+0x61/0x7e Mar 13 10:04:11 Tower kernel: [<ffffffff8104d00c>] __warn+0xb8/0xd3 Mar 13 10:04:11 Tower kernel: [<ffffffff8104d0d4>] warn_slowpath_null+0x18/0x1a Mar 13 10:04:11 Tower kernel: [<ffffffff812dbe08>] btrfs_free_block_groups+0x37a/0x39b Mar 13 10:04:11 Tower kernel: [<ffffffff812eadf9>] close_ctree+0x1d4/0x2e8 Mar 13 10:04:11 Tower kernel: [<ffffffff81137d51>] ? evict_inodes+0x128/0x137 Mar 13 10:04:11 Tower kernel: [<ffffffff812c5c50>] btrfs_put_super+0x14/0x16 Mar 13 10:04:11 Tower kernel: [<ffffffff8112305b>] generic_shutdown_super+0x6a/0xeb Mar 13 10:04:11 Tower kernel: [<ffffffff811232be>] kill_anon_super+0xd/0x17 Mar 13 10:04:11 Tower kernel: [<ffffffff812c5b97>] btrfs_kill_super+0x11/0x94 Mar 13 10:04:11 Tower kernel: [<ffffffff811234b0>] deactivate_locked_super+0x3b/0x68 Mar 13 10:04:11 Tower kernel: [<ffffffff81123e34>] deactivate_super+0x39/0x3c Mar 13 10:04:11 Tower kernel: [<ffffffff8113acd2>] cleanup_mnt+0x53/0x71 Mar 13 10:04:11 Tower kernel: [<ffffffff8113ad24>] __cleanup_mnt+0xd/0xf Mar 13 10:04:11 Tower kernel: [<ffffffff81062530>] task_work_run+0x6a/0x7d Mar 13 10:04:11 Tower kernel: [<ffffffff81002b24>] exit_to_usermode_loop+0x55/0x81 Mar 13 10:04:11 Tower kernel: [<ffffffff81002c61>] syscall_return_slowpath+0x44/0x47 Mar 13 10:04:11 Tower kernel: [<ffffffff8167d344>] entry_SYSCALL_64_fastpath+0xa7/0xa9 Mar 13 10:04:11 Tower kernel: ---[ end trace 8e45affbece91bb8 ]--- Mar 13 10:04:11 Tower kernel: BTRFS info (device loop0): space_info 4 has 993476608 free, is not full Mar 13 10:04:11 Tower kernel: BTRFS info (device loop0): space_info total=1342177280, used=348618752, pinned=0, reserved=16384, may_use=0, readonly=65536 Mar 13 10:04:11 Tower kernel: BTRFS warning (device loop0): page private not zero on page 4524769280 Mar 13 10:04:11 Tower kernel: BTRFS warning (device loop0): page private not zero on page 4524773376 Mar 13 10:04:11 Tower kernel: BTRFS warning (device loop0): page private not zero on page 4524777472 Mar 13 10:04:11 Tower kernel: BTRFS warning (device loop0): page private not zero on page 4524781568 tower-diagnostics-20170313-1030.zip
  10. MisterWolfe

    [Support] Linuxserver.io - Mylar

    Good to know. Thanks.
  11. MisterWolfe

    [Support] Linuxserver.io - Mylar

    I've had some trouble updating mylar to update. The web gui tells me there is a newer version available with 33 new commits. I hit the update option, the web gui goes to an updating page, and then shows me that none of the updates have been applied. Log file gives me this error: 2016-09-22 11:04:37 WARNING Could not get the latest commit from github 2016-09-22 11:04:36 INFO Retrieving latest version information from github I've got it set yp pull from the development branch. I've tried deleting the docker and re-adding it. I've tried creating a new appadata directory with no change. Suggestions?
  12. MisterWolfe

    unRAID Server Release 6.2.0-beta19 Available

    Try running make_bootable in Windows7. Windows 10 didn't allow the make_bootable to run for me, but I was able to run it on a Win 7 OS.
  13. Typically I connect to my vpn through my router. This can complicate certain things for members of my household when on steam. This is why I was testing the client and why I monitored it while it was active to see what kind of footprint was being exposed. Quite large, obviously. I'll check out bixhex's offerings to see if they'll work for me. If not, I'll put a second router on my network for unraid to use for VPN.
  14. The operative word was 'had'. Yes. Using the OpenVPN client. Under controlled circumstances to test the client. Why are you surprised that someone is testing it? I haven't seen other test results from using the openvpn client plugin. I'm curious what others are seeing when they use it. If it's an insecure plugin, perhaps it should be noted somewhere.
  15. I have a concern about the openvpn client on unraid. Several times now I've noticed login attempts to my unraid server while connected to my VPN. My VPN blocks all port forwarding, so I'm not sure how they are connecting to me. You can see a snippet below of the log file. Mar 21 19:09:35 Tower in.telnetd[5987]: connect from 187.22.157.164 (187.22.157.164) Mar 21 19:09:35 Tower telnetd[5987]: ttloop: peer died: EOF Mar 21 19:11:55 Tower in.telnetd[7255]: connect from 221.138.84.57 (221.138.84.57) Mar 21 19:11:55 Tower emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Mar 21 19:12:01 Tower telnetd[7255]: ttloop: peer died: EOF Mar 21 19:13:49 Tower emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Mar 21 19:15:35 Tower in.telnetd[8908]: connect from 187.160.124.138 (187.160.124.138) Mar 21 19:15:38 Tower emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Mar 21 19:15:45 Tower login[8917]: invalid password for 'UNKNOWN' on '/dev/pts/2' from 'CableLink-187-160-124-138.PCs.InterCable.net' Mar 21 19:15:51 Tower login[8917]: invalid password for 'UNKNOWN' on '/dev/pts/2' from 'CableLink-187-160-124-138.PCs.InterCable.net' Mar 21 19:16:10 Tower php: /usr/local/emhttp/plugins/openvpnclient/scripts/rc.openvpnclient 'stop' Mar 21 19:16:12 Tower ntpd[1476]: Deleting interface #8 tun5, 10.8.0.113#123, interface stats: received=0, sent=0, dropped=0, active_time=866 secs As soon as I disconnect from the VPN, the login attempts stop. I've got a query in to my VPN provider asking about the attack surface presented when using their service. I'm beefing up iptables, but my understanding is that while using a VPN with no port forwarding, there shouldn't be a way to route back to my server. This means that either the openvpn client or my VPN is exposing the unraid server to the world. Has anyone else experienced this while connected to a VPN? Thanks,

Copyright © 2005-2018 Lime Technology, Inc.
unRAID® is a registered trademark of Lime Technology, Inc.