dgaschk
-
Posts
8,920 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by dgaschk
-
-
On 1/5/2019 at 5:18 PM, plantsandbinary said:
Trying to get the SFTP docker working but I'm having some trouble. I've read the github page but it isn't exactly clear.
So far I have created the users.conf file and added a single user as mentioned on the github page. The container now starts, but I am unsure whether or not I am supposed to run it in 'host' or 'bridge' or something else. It's just running on port 22. As follows:
I haven't set a directory yet to share, but I want to share the main storage directory. In this case it's "/tank"
The problem is, that I cannot even log in yet with Filezilla on my Windows PC. The connection just keeps timing out. I don't understand why.
Can I get some help?
I'm having the same problem.
I think I've created the home directory.
This is my users.conf:
#user:pass:1001:100 hdhr:hdhr:1002:100
Here is my output:
MacBook-Pro:~ dga$ sftp [email protected]:2222 [email protected]: Permission denied (publickey,keyboard-interactive). Connection closed MacBook-Pro:~ dga$
The unRAID ssh server is configured to only use a key and no passwords. Could those settings be affecting the docker? What additional configuration is needed?
Thanks,
David
docker log:
Mon Jan 28 23:25:04 America 2019 [info] Existing jail.conf found. Copying to container filesystem! Mon Jan 28 23:25:04 America 2019 [info] Existing sshd_config found. Copying to container filesystem! Creating users... [entrypoint] Parsing user data: "hdhr:hdhr:1002:100" * Starting system logging syslog-ng ...done. [entrypoint] Executing sshd * Starting OpenBSD Secure Shell server sshd ...done. [entrypoint] Executing fail2ban * Starting authentication failure monitor fail2ban ...done. Jan 28 23:25:05 c682e4b023fa sshd[71]: Server listening on 0.0.0.0 port 22. Jan 28 23:25:05 c682e4b023fa sshd[71]: Server listening on :: port 22. Mon Jan 28 23:29:44 America 2019 [info] Existing jail.conf found. Copying to container filesystem! Mon Jan 28 23:29:44 America 2019 [info] Existing sshd_config found. Copying to container filesystem! * Starting system logging syslog-ng ...done. [entrypoint] Executing sshd * Starting OpenBSD Secure Shell server sshd ...done. [entrypoint] Executing fail2ban * Starting authentication failure monitor fail2ban ...done. Jan 28 23:29:44 c682e4b023fa sshd[51]: Server listening on 0.0.0.0 port 22. Jan 28 23:29:44 c682e4b023fa sshd[51]: Server listening on :: port 22.
-
This is why I'm inquiring about a docker.
Has anyone used the docker "markusmcnugen/sftp"?
-
“User file access” is a user other than root accessing files on the server. UnRaid supports user file access via AFP, and SMB. (Is NFS still supported?) SSH access is only supported for the root user. User file access via SSH is unsupported.
I’m looking for a plug-in or docker that allows users(other than root) file access via SSH.
-
Whats the easiest way to enable user file access via ssh?
Is there a plugin or docker that allows file access via ssh?
Thanks,
David
-
I have a failing drive that I'm 3X pre-clearing to see if the attributes will stabilize. Pre-clearing this drive makes the entire unRAID webGUI become unresponsive for hours at a time. If I wait long enough the GUI starts responding again. The drive is on its second pre-read and has over 6000 newly reallocated sectors. I know that this is an unusual case but I'm also certain that it will happen again to someone else. Is there anything that can be done to keep the GUI responsive when working with a bad drive?
PS. I can send you the drive if it'll be helpful.
This is in /Main or in /Tools/Preclear page?
Main. The GUI is unresponsive now. I entered "smartctl -a -A /dev/sde &" via ssh and the command has not returned. I think it will eventually. It seems to hang until the zeroing is done.
-
I have a failing drive that I'm 3X pre-clearing to see if the attributes will stabilize. Pre-clearing this drive makes the entire unRAID webGUI become unresponsive for hours at a time. If I wait long enough the GUI starts responding again. The drive is on its second pre-read and has over 6000 newly reallocated sectors. I know that this is an unusual case but I'm also certain that it will happen again to someone else. Is there anything that can be done to keep the GUI responsive when working with a bad drive?
PS. I can send you the drive if it'll be helpful.
-
That message on the console is harmless. It's happening because it's trying to get your MAC address in order to generate the Time Machine avahi service. Not sure why that's happening just yet, but that's not the cause of your webGui hang.
I'll know tomorrow if it hangs in safe mode.
No hang in SAFE-mode.
-
That message on the console is harmless. It's happening because it's trying to get your MAC address in order to generate the Time Machine avahi service. Not sure why that's happening just yet, but that's not the cause of your webGui hang.
I'll know tomorrow if it hangs in safe mode.
-
Upgraded for 6.2.4 to 6.3.0. Web-GUI stopped responding overnight. Rebooted into safe mode. Every time I click on the webGUI the line
ioctl(SIOCGIFHWADDR): Bad address
appears in the console. Every single click generates a line and they sometimes appear spontaneously. Maybe on refresh. Ran memtest overnight without error. Rebooted into safe mode. The Line appears in the console with each interaction and sometimes spontaneously.
See here: http://lime-technology.com/forum/index.php?topic=55052.0
and here: http://lime-technology.com/forum/index.php?topic=56281.0
Thanks.
-
Ran Memtext overnight. There were no errors. Running in SAFE-mode and still seeing the line appear on the console with each interaction of the Web-GUI. Please help!
-
I'm getting this in SAFE-mode. I've started a thread under Defect Reports.
-
Updated to 6.3.0 and the weGUI locked up overnight. SSH and share were still available. Rebooted into SAFE-mode and the line "ioctl(SIOCGIFHWADDR): Bad address" is appearing on the console every time I click on the webGUI. I think it also appears to happen on refresh. Still running is SAFE-mode.
More discussion here: http://lime-technology.com/forum/index.php?topic=55052.0
-
Cheers. Will delete it in a moment.
FWIW I noticed that the error stops after I stop the array.
EDIT: Deleted dynamix.plg while in safe mode, then rebooted. I still get the error.
Same here.
WebGUI locks up after 24 hours. Shares and SSH access are still available. Just no WebGUI.
Deleted dynamix.plg
Rebooted into safe mode. Every time I click on the webGUI the line " ioctl(SIOCGIFHWADDR): Bad address" appears in the console. Every single click generates a line and they sometimes appear spontaneously. Maybe on refresh.
Any ideas? This looks like a bug.
-
Im also still getting this message:
error: Ignoring tor because of bad file mode - must be 0644 or 0444.
Statistics just sent via tor; succeeded for the first time.
-
Each function the script run in parallel fork the script into another pid, simple as that.
Let's see. In clearing operation, we have the parent PID, the write function PID, display refresh function PID, and so goes on...
OK, so that's normal. Any advise on the "missing csrf_token"?
I updated Unassigned Devices and I think its fixed.
-
Any answer for this? I started seeing it when I updated from 6.2.4 to 6.3.0.
-
Both plugins have been updated to handle these errors. It looks like you don't have the latest versions installed. The latest version of UD is 2017.02.04.
You are correct sir. Thank you.
-
Each function the script run in parallel fork the script into another pid, simple as that.
Let's see. In clearing operation, we have the parent PID, the write function PID, display refresh function PID, and so goes on...
OK, so that's normal. Any advise on the "missing csrf_token"?
-
Im also still getting this message:
error: Ignoring tor because of bad file mode - must be 0644 or 0444.
-
This is repeating over and over again on two servers that where updated to 6.3.0 last night. All plugins are current.
Feb 4 01:38:18 rack root: error: plugins/preclear.disk/Preclear.php: missing csrf_token
Feb 4 01:38:19 rack root: error: plugins/unassigned.devices/UnassignedDevices.php: missing csrf_token
Feb 4 01:38:25 rack root: error: plugins/unassigned.devices/UnassignedDevices.php: missing csrf_token
Feb 4 01:38:29 rack root: error: plugins/preclear.disk/Preclear.php: missing csrf_token
Feb 4 01:38:31 rack root: error: plugins/unassigned.devices/UnassignedDevices.php: missing csrf_token
Feb 4 01:38:37 rack root: error: plugins/unassigned.devices/UnassignedDevices.php: missing csrf_token
Feb 4 01:38:40 rack root: error: plugins/preclear.disk/Preclear.php: missing csrf_token
Feb 4 01:38:43 rack root: error: plugins/unassigned.devices/UnassignedDevices.php: missing csrf_token
Feb 4 01:38:49 rack root: error: plugins/unassigned.devices/UnassignedDevices.php: missing csrf_token
Feb 4 01:38:51 rack root: error: plugins/preclear.disk/Preclear.php: missing csrf_token
Thanks.
-
This is repeating over and over again on two servers that where updated to 6.3.0 last night. All plugins are current.
Feb 4 01:38:18 rack root: error: plugins/preclear.disk/Preclear.php: missing csrf_token
Feb 4 01:38:19 rack root: error: plugins/unassigned.devices/UnassignedDevices.php: missing csrf_token
Feb 4 01:38:25 rack root: error: plugins/unassigned.devices/UnassignedDevices.php: missing csrf_token
Feb 4 01:38:29 rack root: error: plugins/preclear.disk/Preclear.php: missing csrf_token
Feb 4 01:38:31 rack root: error: plugins/unassigned.devices/UnassignedDevices.php: missing csrf_token
Feb 4 01:38:37 rack root: error: plugins/unassigned.devices/UnassignedDevices.php: missing csrf_token
Feb 4 01:38:40 rack root: error: plugins/preclear.disk/Preclear.php: missing csrf_token
Feb 4 01:38:43 rack root: error: plugins/unassigned.devices/UnassignedDevices.php: missing csrf_token
Feb 4 01:38:49 rack root: error: plugins/unassigned.devices/UnassignedDevices.php: missing csrf_token
Feb 4 01:38:51 rack root: error: plugins/preclear.disk/Preclear.php: missing csrf_token
One of the servers that was running 3 pre-clears has an unresponsive webGUI and these processes:
root@rack:~# ps x | grep emhttp 7532 ? Sl 4:27 /usr/local/sbin/emhttp
9425 ? S 0:00 /bin/sh -c /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null
9426 ? S 0:00 /usr/bin/php -q /usr/local/emhttp/plugins/dynamix/scripts/monitor
12950 pts/0 S+ 1:42 /bin/bash /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --cycles 3 --no-prompt /dev/sde
12951 pts/0 S+ 0:00 /bin/bash /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --cycles 3 --no-prompt /dev/sde
12952 pts/0 S+ 0:00 /bin/bash /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --cycles 3 --no-prompt /dev/sde
12953 pts/0 S+ 0:00 /bin/bash /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --cycles 3 --no-prompt /dev/sde
12954 pts/0 S+ 0:00 /bin/bash /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --cycles 3 --no-prompt /dev/sde
16299 pts/1 S+ 2:01 /bin/bash /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --cycles 1 --no-prompt /dev/sdk
16300 pts/1 S+ 0:00 /bin/bash /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --cycles 1 --no-prompt /dev/sdk
16301 pts/1 S+ 0:00 /bin/bash /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --cycles 1 --no-prompt /dev/sdk
16302 pts/1 S+ 0:00 /bin/bash /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --cycles 1 --no-prompt /dev/sdk
16303 pts/1 S+ 0:00 /bin/bash /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --cycles 1 --no-prompt /dev/sdk
17805 pts/2 S+ 1:46 /bin/bash /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --cycles 1 --no-prompt /dev/sdp
17806 pts/2 S+ 0:00 /bin/bash /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --cycles 1 --no-prompt /dev/sdp
17807 pts/2 S+ 0:00 /bin/bash /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --cycles 1 --no-prompt /dev/sdp
17808 pts/2 S+ 0:00 /bin/bash /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --cycles 1 --no-prompt /dev/sdp
17809 pts/2 S+ 0:00 /bin/bash /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --cycles 1 --no-prompt /dev/sdp
25115 ? S 0:00 /bin/sh -c /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugincheck &> /dev/null
25125 ? S 0:00 /usr/bin/php -q /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugincheck
26762 pts/3 S+ 0:00 grep emhttp
26895 pts/0 S+ 0:00 /bin/bash /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --cycles 3 --no-prompt /dev/sde
27829 ? S 0:00 sh -c smartctl -n standby -A '/dev/sdp' > '/var/local/emhttp/smart/sdp'
root@rack:~#
The other server is running 1 preclear and its webGUI is responsive. This server has these processes:
root@Othello:~# ps x | grep emhttp
7501 ? Sl 2:18 /usr/local/sbin/emhttp
8528 pts/0 S+ 0:00 /bin/bash /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --cycles 1 --no-prompt /dev/sdj
12415 pts/0 S+ 2:51 /bin/bash /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --cycles 1 --no-prompt /dev/sdj
12416 pts/0 S+ 0:00 /bin/bash /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --cycles 1 --no-prompt /dev/sdj
12417 pts/0 S+ 0:00 /bin/bash /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --cycles 1 --no-prompt /dev/sdj
12418 pts/0 S+ 0:00 /bin/bash /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --cycles 1 --no-prompt /dev/sdj
12419 pts/0 S+ 0:00 /bin/bash /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --cycles 1 --no-prompt /dev/sdj
31923 pts/1 S+ 0:00 grep emhttp
root@Othello:~#
Why so many bash processes?
Thanks.
-
It may increase the rigor of the testing without requiring additional time.
-
Enhancement Request:
Option to alternate between writing 0's and 1's. If I choose an odd number of passes then start with 0's and if even start with 1's. The last pass should always zero.
Thanks for all the hard work.
-
I received this message from a server overnight,
"error: Ignoring tor because of bad file mode - must be 0644 or 0444."
When I click Send it seams to hang. I waited a few minutes and then reloaded the page. I then hit Dismiss.
User file access via SSH
in General Support
Posted
I got this working using docgyver's SSH Config Tool plugin and a few lines of bash to symlink the home directory.