Beiträge von psy-q

    Duplicati is crashing every time I try and run a new B2 backup (~500GB). Haven't found anything here or on the Duplicati fourm to help so far.


    Duplicati says this:

    OMV Log says this:

    Code
    Sep  4 10:40:52 openmediavault duplicati-server[3152]: [ERROR] FATAL UNHANDLED EXCEPTION: System.OutOfMemoryException: Out of memory
    Sep  4 10:40:52 openmediavault duplicati-server[3152]: at <0x00000> <unknown method>
    Sep  4 10:40:52 openmediavault duplicati-server[3152]: at (wrapper alloc) object:AllocVector (intptr,intptr)
    Sep  4 10:40:52 openmediavault duplicati-server[3152]: at Mono.Security.ASN1..ctor (System.Byte[] data) [0x00000] in <filename unknown>:0
    Sep  4 10:40:52 openmediavault duplicati-server[3152]: at Mono.Security.X509.X509Certificate.get_RSA () [0x00000] in <filename unknown>:0
    Sep  4 10:40:52 openmediavault duplicati-server[3152]: at System.Security.Cryptography.X509Certificates.X509Store.Open (OpenFlags flags) [0x00000] in <filename unknown>:0
    Sep  4 10:40:52 openmediavault duplicati-server[3152]: at System.Security.Cryptography.X509Certificates.X509Chain.get_UserRootStore () [0x00000] in <filename unknown>:0

    I made the changes I found here:
    http://getnosleep.blogspot.ca/…acifs-access-windows.html


    It works... so far. I've had it work then stop working before, so I'm dubious. We'll see how it goes, but at least this will give anyone else that finds the thread in a search some hope.


    Yeah we can get a teamviewer session going. When is best for you?


    The error in the syslog has changed to this:
    Aug 17 16:56:02 NAS-OMV smbd[22933]: [2014/08/17 16:56:02.731191, 2] smbd/service.c:587(create_connection_server_info)
    Aug 17 16:56:02 NAS-OMV smbd[22933]: guest user (from session setup) not permitted to access this share (cloud)
    Aug 17 16:56:02 NAS-OMV smbd[22933]: [2014/08/17 16:56:02.731277, 1] smbd/service.c:678(make_connection_snum)
    Aug 17 16:56:02 NAS-OMV smbd[22933]: create_connection_server_info failed: NT_STATUS_ACCESS_DENIED


    Not sure what caused the change, but the reference to "guest user" seems a little weird.

    Since Samba is basically a package for facilitating transfers between Linux and Windows, I never even thought to test it in Linux. Ubuntu works fine, so it seems to be a Windows related issue.


    I'll probably be able to narrow it down now and let everyone know what it was. Seems funny that a lot of people aren't having the same issues. It affects 3 computers in my home running Windows 7/8 and 8.1

    Reboot the computer you're using to access your shares inbetween config changes. Windows sometimes is unable to recognize the changes.


    Greetings
    David


    Tried that a couple times. Also just tested it on my wife's machine that I haven't touched yet. Same problem.


    Does this help from my syslog? A quick Google of it never really got me an answer.


    Aug 16 14:18:34 NAS-OMV smbd[2028]: [2014/08/16 14:18:34.552070, 1] smbd/service.c:678(make_connection_snum)
    Aug 16 14:18:34 NAS-OMV smbd[2028]: create_connection_server_info failed: NT_STATUS_ACCESS_DENIED
    Aug 16 14:18:34 NAS-OMV smbd[2028]: [2014/08/16 14:18:34.553868, 1] smbd/service.c:678(make_connection_snum)
    Aug 16 14:18:34 NAS-OMV smbd[2028]: create_connection_server_info failed: NT_STATUS_ACCESS_DENIED
    Aug 16 14:18:39 NAS-OMV smbd[2028]: [2014/08/16 14:18:39.164432, 1] smbd/service.c:678(make_connection_snum)
    Aug 16 14:18:39 NAS-OMV smbd[2028]: create_connection_server_info failed: NT_STATUS_ACCESS_DENIED
    Aug 16 14:18:39 NAS-OMV smbd[2028]: [2014/08/16 14:18:39.165731, 1] smbd/service.c:678(make_connection_snum)
    Aug 16 14:18:39 NAS-OMV smbd[2028]: create_connection_server_info failed: NT_STATUS_ACCESS_DENIED
    Aug 16 14:18:43 NAS-OMV smbd[2028]: [2014/08/16 14:18:43.767228, 1] smbd/service.c:678(make_connection_snum)
    Aug 16 14:18:43 NAS-OMV smbd[2028]: create_connection_server_info failed: NT_STATUS_ACCESS_DENIED
    Aug 16 14:18:43 NAS-OMV smbd[2028]: [2014/08/16 14:18:43.769358, 1] smbd/service.c:678(make_connection_snum)
    Aug 16 14:18:43 NAS-OMV smbd[2028]: create_connection_server_info failed: NT_STATUS_ACCESS_DENIED
    Aug 16 14:18:46 NAS-OMV smbd[2028]: [2014/08/16 14:18:46.075915, 1] smbd/service.c:678(make_connection_snum)
    Aug 16 14:18:46 NAS-OMV smbd[2028]: create_connection_server_info failed: NT_STATUS_ACCESS_DENIED

    The double slash thing is from the Shared Folders setup. Not sure why OMV puts that in automatically, but I've removed it. Didn't help :(


    I've done so many things trying to correct permission problems that I've probably messed them up good and proper at this point. Everything in ACL is disabled, but set for RW in owner and group. Privileges are set as RW for my user. Does samba care which owner and group have control over the folder?


    What permissions specifically are samba looking at? I'm ok with tinkering in the CLI, but not really sure what samba is doing.

    I hate to make another Samba permission related thread, but this has been driving me insane for HOURS. Can't sleep....


    Public works fine on my WIndows 8.1 machine. Cannot get private to work correctly. Windows just keeps saying it's not accessible, you might not have permission to access this network resource yada yada. Right after I put in my user:pass.


    I've looked EVERYWHERE for similar cases and help tracking down the issue. Total overload. There is just way too much information with way too many ways of diagnosing. MAN pages are great when you need something specific, but 50 pages of parameters that you don't need is overwhelming.


    Lets start with this:

    Code
    root@NAS-OMV:/media/95cc7417-ca5c-4041-85bc-5d67e76f0da8# ls -al
    total 40
    drwxr-xr-x  6 root           users           4096 Aug 15 10:24 .
    drwxr-xr-x  7 root           root            4096 Aug 15 11:36 ..
    drwxrwsr-x+ 7 nobody         users           4096 Aug 15 10:25 cloud
    drwxr-xr-x  2 root           root           16384 Aug 14 20:53 lost+found
    -rwxr-xr-x  1 root           root             412 Aug 14 22:44 mount.json
    drwxr-sr-x  3 openmediavault openmediavault  4096 Aug 14 22:44 owncloud
    drwxr-xr-x  2 root           root            4096 Aug 14 22:57 tmp


    "cloud" is the one I'm trying to share. Works fine if I set it to public.


    smb.conf:


    stat:

    Code
    root@NAS-OMV:/media/95cc7417-ca5c-4041-85bc-5d67e76f0da8# stat cloud
      File: `cloud'
      Size: 4096            Blocks: 8          IO Block: 4096   directory
    Device: 811h/2065d      Inode: 46006273    Links: 7
    Access: (2775/drwxrwsr-x)  Uid: (65534/  nobody)   Gid: (  100/   users)
    Access: 2014-08-15 22:29:13.864207246 -0700
    Modify: 2014-08-15 10:25:31.907985486 -0700
    Change: 2014-08-15 22:46:17.632181188 -0700


    Now excuse me while I take a break with a bottle of Jack Daniels and cry my frustration away ;(

    The search system on the board is just killing me. Impossible to find anything. If I see this one more time I'm going to kick a puppy...


    The following words in your search query were ignored because they are too common words

    Anyone know why the GUI keeps setting my path in Transmission to something like this? With the extra slashes on the end.


    /media/adaa55b9-b1d6-4d97-8701-905b7447ac0d///

    I'm running my VPN on a second router (RT-N66U w/Shibby Tomato). DHCP is disabled but I gave it a static IP and setup an OpenVPN client to my VPN. Then I just change whatever device I want to use the VPN to a static IP with the VPN router as the gateway (works wonders on my Xbox 360). Offloads all the VPN traffic work to another device and keeps my primary router happy and oblivious. Transmission works perfect.


    If the VPN goes down it'll probably default to a standard connection, but if you're ambitious enough I'm sure the iptables on either OMV or the router could be manipulated to correct that.


    Sometimes it's better to keep it simple, although I totally understand the need to bend the software to your will ;)

    I just installed a clean version of 0.5 from 0.4 and noticed my external drives (USB2) were not mounting at boot. This seemed to be a normal function in 0.4, so before I go hacking away at the system I just wanted to make sure it was intended. They work fine when mounted but then don't re-mount after the system restarts.


    My machine is a bit unusual. Atom N2800, laptop power supply, OCZ Agility2 60GB SSD system drive. My external drives are just basic WDs that I had lying around, there are no internal drives in the machine yet, except the system drive.