[OmniOS-discuss] 4k sectors on a kvm guest
hi, before running a real hardware omnios host I am learning how to use it in a kvm vm running on centos. The disk performance is quite poor, this is partly due to omnios not using virtio hard drives but ide drives. But I think the root zpool is not properly aligned either: root@testomnios:~# zdb -C rpool | grep ashift ashift: 9 this should be 12 to be aligned to 4k sectors I understand. Is there a way to change this? TIA, -- Groeten, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] trouble mirroring the zpool rpool
hi, I have installed omnios with a 32GiB usb stick as the rpool. I have two of those sticks, so I would like to mirror them. rmformat tells me this about the usb sticks: # rmformat Looking for devices... 1. Logical Node: /dev/rdsk/c14t0d0p0 Physical Node: /pci@0,0/pci103c,1609@12,2/storage@3/disk@0,0 Connected Device: Patriot Memory PMAP Device Type: Removable Bus: USB Size: 30.2 GB Label: None Access permissions: Medium is not write protected. 2. Logical Node: /dev/rdsk/c15t0d0p0 Physical Node: /pci@0,0/pci103c,1609@12,2/storage@4/disk@0,0 Connected Device: Patriot Memory PMAP Device Type: Removable Bus: USB Size: 30.2 GB Label: None Access permissions: Medium is not write protected. The sticks are exactly the same brand and model, so they should be exactly equal. In order to mirror the rpool I followed the instructions in http://wiki.openindiana.org/oi/2.1+Post-installation This is rpool now: # zpool status rpool pool: rpool state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM rpoolONLINE 0 0 0 c14t0d0s0 ONLINE 0 0 0 errors: No known data errors But when I try the procedure in the openindiana wiki I get this: # fdisk -B c15t0d0p0 # prtvtoc /dev/rdsk/c14t0d0s2 | fmthard -s - /dev/rdsk/c15t0d0s2 fmthard: Partition 2 specifies the full disk and is not equal full size of disk. The full disk capacity is 61705665 sectors. fmthard: Partition 2 specified as 61737795 sectors starting at 0 does not fit. The full disk contains 61705665 sectors. fmthard: New volume table of contents now in place. # zpool attach rpool c14t0d0s0 c15t0d0s0 invalid vdev specification use '-f' to override the following errors: /dev/dsk/c15t0d0s0 overlaps with /dev/dsk/c15t0d0s2 So apparently the 2 sticks are not exactly the same. Now I got brave (haha) and used the -f swith and it works: # zpool attach -f rpool c14t0d0s0 c15t0d0s0 Make sure to wait until resilver is done before rebooting. # zpool status pool: rpool state: ONLINE status: One or more devices is currently being resilvered. The pool will continue to function, possibly in a degraded state. action: Wait for the resilver to complete. scan: resilver in progress since Mon May 6 20:33:17 2013 53.2M scanned out of 7.13G at 1.06M/s, 1h53m to go 51.0M resilvered, 0.73% done config: NAME STATE READ WRITE CKSUM rpool ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 c14t0d0s0 ONLINE 0 0 0 c15t0d0s0 ONLINE 0 0 0 (resilvering) errors: No known data errors Is this expected behaviour? -- Groeten, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] trouble mirroring the zpool rpool
hi, fwiw, it worked: # zpool status rpool pool: rpool state: ONLINE scan: resilvered 7.14G in 0h26m with 0 errors on Mon May 6 20:59:19 2013 config: NAME STATE READ WRITE CKSUM rpool ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 c14t0d0s0 ONLINE 0 0 0 c15t0d0s0 ONLINE 0 0 0 errors: No known data errors strange though (for me at least, if I see such an error as 'use '-f' to override the following errors: /dev/dsk/c15t0d0s0 overlaps with /dev/dsk/c15t0d0s2' it makes me nervous). -- groet, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] nfsv4 acls wtf moment
hi Siggi, On Fri, May 10, 2013 at 3:47 PM, Sigbjorn Lie sigbj...@nixtra.com wrote: Hi, Did you set aclmode to passthrough too? no but I just tried it and the linux nfsv4 client still ignores the inheritance: # zfs get all tank/testshare | grep acl tank/testshare aclmode passthrough local tank/testshare aclinheritpassthrough local Thanks for the suggestion. -- natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] nfsv4 acls wtf moment
On Sat, May 11, 2013 at 10:35 PM, Paul B. Henson hen...@acm.org wrote: On Sat, May 11, 2013 at 09:12:43AM +0200, Natxo Asenjo wrote: I have straced the cp -r command with discard and restricted aclmode settings (see attachments). open(/net/zfstank.ipa.asenjo.nx/tank/testshare/bin/parsetable.pl, O_WRONLY|O_CREAT|O_EXCL, 0664) = 4 Yeah, you're getting bit by the NFS exclusive open issue. Basically, NFS up to v4 overloads the mode bits to store a verifier to check on whether the exclusive part of the open succeeded, and then does a separate setattr afterwards to set the actual mode. So what happens is the initial open results in a file with the right inherited ACL, and the subsequent setattr results in the same change as an explicit chmod, typically breaking the ACL. This is fixed in the NFS v4.1 spec, but that's not really in use yet. Theoretically it should be possible to keep some state on the server side and work around this issue, but I've never had the time to dig into it. ok, thanks for your explanation. I had indeed seen all those 0664 that pointed in that direction. I see the illumos nfs 4.1 project is a bti 'inactive' ;-), but it'll come one day I guess. Does the linux nfs client complain at all when you do the copy with aclmode=restricted? The client would get a success for the open, but the following setattr op would fail, and I wasn't sure how the nfs client would deal with that. From the strace output it looks like the underlying nfs setattr failure isn't passed back up to the userland code, it looks like the open just succeeds as normal. Cool. no, it does when moving a file though : $ mv testmove /net/zfstank.ipa.asenjo.nx/tank/testshare/ mv: preserving permissions for `/net/zfstank.ipa.asenjo.nx/tank/testshare/testmove': Operation not permitted but that is not really a showstopper. The file gets copied and the permissions are applied: $ nfs4_getfacl /net/zfstank.ipa.asenjo.nx/tank/testshare/testmove A::EVERYONE@:rwadxtTnNcCoy I had not noticed it until yesterday because I am used to copying first and removing later (lost some files once because of a hardware failure and got used to doing that since then). I'm glad somebody's finding aclmode=restricted useful :). I'm surprised that not more people are using this! Thanks for implementing it. -- groet, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] server spontanously reboots on cifs action
hi, today twice I have experimented this while removing a (largish) folder infrastructure with plenty of pictures. I was removing the folder first with the windows explorer and then with the command rd /s /q in a cmd.exe prompt. This does not happen when removing the same folder directly on the server. The user has no administrative privileges. The hardware is a microserver HP N40L, with the rpool on 2 usb sticks. Could this be the problem? The data pool where the files where is a raidz pool with 4 3TiB disks (wd red). Where can I find more info on this? /var/adm/messages shows nothing relevant. My solaris knowlegde is too limitied yet. TIA, -- Groeten, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] nfsv4 acls wtf moment
On Wed, May 15, 2013 at 11:47 PM, Paul B. Henson hen...@acm.org wrote: On 5/12/2013 1:21 PM, Natxo Asenjo wrote: mm, when using scp it bypasses the acl as well ..., grrr. Even with aclmode=restricted? strangely enough, on one share yes, the other no. The difference is the share root dir permissions # /bin/ls -vd /tank/testshare/ drwxrwxrwx+ 10 root root 10 May 16 07:31 /tank/testshare/ 0:everyone@:list_directory/read_data/add_file/write_data /add_subdirectory/append_data/read_xattr/write_xattr/execute /delete_child/read_attributes/write_attributes/delete/read_acl /write_acl/write_owner/synchronize:file_inherit/dir_inherit:allow # bin/ls -vd /tank/fotos/ d-+289 root root 290 May 16 07:32 /tank/fotos/ 0:user:username:list_directory/read_data/add_file/write_data /add_subdirectory/append_data/read_xattr/write_xattr/execute /delete_child/read_attributes/write_attributes/delete/read_acl /write_acl/write_owner/synchronize:file_inherit/dir_inherit:allow on the /tank/fotos, when I scp as root the root umask sets extra aces, on the /tank/testshare dir when I scp as root the ace is respected root@zfstank:~# zfs get all tank/testshare | grep acl tank/testshare aclmode restricted local tank/testshare aclinheritpassthrough local root@zfstank:~# zfs get all tank/fotos | grep acl tank/fotos aclmode restricted local tank/fotos aclinheritpassthroughlocal $ scp -r dosbox/ root@zfstank:/tank/testshare/testdir # /bin/ls -vd /tank/testshare/testdir/ drwxrwxrwx+ 4 root root 5 May 16 22:03 /tank/testshare/testdir/ 0:everyone@:list_directory/read_data/add_file/write_data /add_subdirectory/append_data/read_xattr/write_xattr/execute /delete_child/read_attributes/write_attributes/delete/read_acl /write_acl/write_owner/synchronize:file_inherit/dir_inherit /inherited:allow $ scp -r dosbox/ root@zfstank:/tank/fotos/testdir # /bin/ls -vd /tank/fotos/testdir drwxr-xr-x+ 4 root root 5 May 16 22:03 /tank/fotos/testdir/ 0:user:username:list_directory/read_data/add_file/write_data /add_subdirectory/append_data/read_xattr/write_xattr/execute /delete_child/read_attributes/write_attributes/delete/read_acl /write_acl/write_owner/synchronize:file_inherit/dir_inherit /inherited:allow 1:owner@:list_directory/read_data/add_file/write_data/add_subdirectory /append_data/read_xattr/write_xattr/execute/read_attributes /write_attributes/read_acl/write_acl/write_owner/synchronize:allow 2:group@:list_directory/read_data/read_xattr/execute/read_attributes /read_acl/synchronize:allow 3:everyone@:list_directory/read_data/read_xattr/execute/read_attributes /read_acl/synchronize:allow strange. I am going to open a bug with redhat to see if they can get to fix coreutils and the ssh client to respect nfsv4 aces instead of bypassing the stuff. We'll see. -- groet, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] sudo ldap
hi, has anyone pointers on how to configure this in omnios? -- Groeten, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] upgrade nearly perfect
hi, I just followed the instructions on the wiki http://omnios.omniti.com/wiki.php/Upgrade_r151006_r151008 and everything worked fine, except now is java broken: # /usr/java/bin/java -version ld.so.1: java: fatal: libjli.so: open failed: No such file or directory Killed # ldd /usr/bin/java libthread.so.1 = /lib/libthread.so.1 libjli.so = (file not found) libdl.so.1 = /lib/libdl.so.1 libc.so.1 = /lib/libc.so.1 libm.so.2 = /lib/libm.so.2 This is causing the backup software (crashplan) to fail. As far as I can see, my root zone only has this publisher: # pkg publisher PUBLISHER TYPE STATUS URI omniosorigin online http://pkg.omniti.com/omnios/release/ reverting to the former version fixes java and crashplan works again: # /usr/java/bin/java -version java version 1.6.0_26 Java(TM) SE Runtime Environment (build 1.6.0_26-b03) Java HotSpot(TM) Server VM (build 20.1-b02, mixed mode) # ldd /usr/bin/java libthread.so.1 = /lib/libthread.so.1 libjli.so = /usr/jdk/instances/jdk1.6.0/bin/../jre/lib/i386/jli/libjli.so libdl.so.1 = /lib/libdl.so.1 libc.so.1 = /lib/libc.so.1 libm.so.2 = /lib/libm.so.2 I see in the release changelog that oracle java was replaced by openjdk, so I think I found the reason it fails ;-), but now the question remains, where is the openjdk java ... I will keep searching, but maybe someone has already found this problem. TIA, Groeten, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] upgrade nearly perfect
-- Groeten, natxo On Fri, Dec 13, 2013 at 1:41 PM, Chavdar Ivanov c...@outlook.com wrote: -Original Message- From: OmniOS-discuss [mailto:omnios-discuss-boun...@lists.omniti.com] On Behalf Of Natxo Asenjo Sent: 13 December 2013 12:06 To: omnios-discuss@lists.omniti.com Subject: [OmniOS-discuss] upgrade nearly perfect hi, I just followed the instructions on the wiki http://omnios.omniti.com/wiki.php/Upgrade_r151006_r151008 and everything worked fine, except now is java broken: # /usr/java/bin/java -version ld.so.1: java: fatal: libjli.so: open failed: No such file or directory Killed # ldd /usr/bin/java libthread.so.1 = /lib/libthread.so.1 libjli.so = (file not found) libdl.so.1 = /lib/libdl.so.1 libc.so.1 = /lib/libc.so.1 libm.so.2 = /lib/libm.so.2 This is causing the backup software (crashplan) to fail. As far as I can see, my root zone only has this publisher: # pkg publisher PUBLISHER TYPE STATUS URI omniosorigin online http://pkg.omniti.com/omnios/release/ reverting to the former version fixes java and crashplan works again: # /usr/java/bin/java -version java version 1.6.0_26 Java(TM) SE Runtime Environment (build 1.6.0_26-b03) Java HotSpot(TM) Server VM (build 20.1-b02, mixed mode) # ldd /usr/bin/java libthread.so.1 = /lib/libthread.so.1 libjli.so = /usr/jdk/instances/jdk1.6.0/bin/../jre/lib/i386/jli/libjli.so libdl.so.1 = /lib/libdl.so.1 libc.so.1 = /lib/libc.so.1 libm.so.2 = /lib/libm.so.2 I see in the release changelog that oracle java was replaced by openjdk, so I think I found the reason it fails ;-), but now the question remains, where is the openjdk java ... I will keep searching, but maybe someone has already found this problem. [[ci]] My update didn't have that problem: ➜ ~ cat /etc/release OmniOS v11 r151008 Copyright 2013 OmniTI Computer Consulting, Inc. All rights reserved. Use is subject to license terms. ➜ ~ uname -a SunOS uksup5 5.11 omnios-6de5e81 i86pc i386 i86pc ➜ ~ /usr/java/bin/java -version openjdk version 1.7.0_06 OpenJDK Runtime Environment (build 1.7.0_06-b24) OpenJDK Server VM (build 24.0-b47, mixed mode) ➜ ~ pkg list | grep -i java developer/java/jdk (omnios) 1.7.0.6.24-0.151007 i-- runtime/java (omnios) 1.7.0.6.24-0.151007 i-- ➜ ~ pkg list | grep -i jre I do have omniti repo, but as far as I can see, java comes from the main one. ➜ ~ pkg publisher PUBLISHER TYPE STATUS URI ms.omniti.com(non-sticky) origin online http://pkg.omniti.com/omniti-ms/ omniosorigin online http://pkg.omniti.com/omnios/release/ Chavdar Ivanov TIA, Groeten, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] upgrade nearly perfect
On Fri, Dec 13, 2013 at 4:29 PM, John D Groenveld jdg...@elvis.arl.psu.edu wrote: In message cahbejzw5o2s3w5f42u1yt+av8x1cknq4szadglvm21zmgyp...@mail.gmail.com , Natxo Asenjo writes: Is this the right one? How can I reinstall it or verify it is correctly installed? Looks like OmniTI's /usr/bin/java is linked to the wrong libjli.so. # pkg search libjli.so # pkg install pkg:/developer/java/jdk # /usr/bin/java -version aha! That looks like the solution. In the http://omnios.omniti.com/wiki.php/KYSTY fashion, I had already downloaded java from oracle and got it running in the meantime, but I am going to try this as well, although I do not really see why I need the jdk when I just want the jre. Thanks, I did not know you could use pkg search for files as well, very nice tip. -- Groet, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] zoneadm -z zone attach -u fails
hi, Following the update I needed to update my only non-global zone as well but this is the result: # /usr/sbin/zoneadm -z zone1 attach -u Log File: /var/tmp/zone1.attach_log.X6ai9c Attach Path: /tank/zones/zone1/root Attach ZFS Dataset: tank/zones/zone1/ROOT/zbe-1 Installing: Using pre-existing data in zonepath Result: Attach Failed. And in the log: [Fri Dec 13 16:38:35 CET 2013] Log File: /var/tmp/zone1.attach_log.X6ai9c [Fri Dec 13 16:38:38 CET 2013]Attach Path: /tank/zones/zone1/root [Fri Dec 13 16:38:38 CET 2013] Attach ZFS Dataset: tank/zones/zone1/ROOT/zbe-1 [Fri Dec 13 16:38:38 CET 2013] existing [Fri Dec 13 16:38:38 CET 2013] Installing: Using pre-existing data in zonepath [Fri Dec 13 16:38:38 CET 2013] Sanity Check: Passed. Looks like an OpenSolaris system. Unable to get preferred publisher information for zone 'global'. brand-specific usage: attach [-a archive] [-d dataset] [-n] [-r zfs-recv] [-u] The -a archive option specifies a tar file or cpio archive. The -d dataset option specifies an existing dataset. The -r zfs-recv option receives the output of a 'zfs send' command of an existing zone root dataset. The -u option indicates that the software should be updated to match the current host. [Fri Dec 13 16:38:43 CET 2013] Result: Attach Failed. Any clues? -- Groeten, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] SSH over HTTPS
On Mon, Dec 16, 2013 at 8:46 PM, Michael Mounteney gat...@landcroft.co.uk wrote: Hello, to get around super-tight restrictions in my workplace, I'm looking for an SSH over HTTPS solution. My home server runs OmniOS (of course) and my workplace is a M$ shop through and through. Running sshd on port 443, and connecting via Putty, doesn't work. I don't know why as surely their firewall must allow https traffic, but it doesn't. I don't understand these things fully. have you tried this: http://dag.wiee.rs/howto/ssh-http-tunneling/ -- groet, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] SSH over HTTPS
or maybe this: http://en.wikipedia.org/wiki/Web-based_SSH -- Groeten, natxo On Tue, Dec 17, 2013 at 9:57 AM, Natxo Asenjo natxo.ase...@gmail.com wrote: On Mon, Dec 16, 2013 at 8:46 PM, Michael Mounteney gat...@landcroft.co.uk wrote: Hello, to get around super-tight restrictions in my workplace, I'm looking for an SSH over HTTPS solution. My home server runs OmniOS (of course) and my workplace is a M$ shop through and through. Running sshd on port 443, and connecting via Putty, doesn't work. I don't know why as surely their firewall must allow https traffic, but it doesn't. I don't understand these things fully. have you tried this: http://dag.wiee.rs/howto/ssh-http-tunneling/ -- groet, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] zoneadm -z zone attach -u fails
On Fri, Dec 13, 2013 at 5:26 PM, Chris Nehren cnehren+omnios-disc...@omniti.com wrote: On Fri, Dec 13, 2013 at 16:52:31 +0100, Natxo Asenjo wrote: hi, Following the update I needed to update my only non-global zone as well but this is the result: # /usr/sbin/zoneadm -z zone1 attach -u Log File: /var/tmp/zone1.attach_log.X6ai9c Attach Path: /tank/zones/zone1/root Attach ZFS Dataset: tank/zones/zone1/ROOT/zbe-1 Installing: Using pre-existing data in zonepath Result: Attach Failed. And in the log: [Fri Dec 13 16:38:35 CET 2013] Log File: /var/tmp/zone1.attach_log.X6ai9c [Fri Dec 13 16:38:38 CET 2013]Attach Path: /tank/zones/zone1/root [Fri Dec 13 16:38:38 CET 2013] Attach ZFS Dataset: tank/zones/zone1/ROOT/zbe-1 [Fri Dec 13 16:38:38 CET 2013] existing [Fri Dec 13 16:38:38 CET 2013] Installing: Using pre-existing data in zonepath [Fri Dec 13 16:38:38 CET 2013] Sanity Check: Passed. Looks like an OpenSolaris system. Unable to get preferred publisher information for zone 'global'. brand-specific usage: attach [-a archive] [-d dataset] [-n] [-r zfs-recv] [-u] The -a archive option specifies a tar file or cpio archive. The -d dataset option specifies an existing dataset. The -r zfs-recv option receives the output of a 'zfs send' command of an existing zone root dataset. The -u option indicates that the software should be updated to match the current host. [Fri Dec 13 16:38:43 CET 2013] Result: Attach Failed. Any clues? This is an issue that we're looking into fixing. It looks like the zone attach script is expecting output that isn't there, or output in another format. More to come when we know more. Is there a tracker where one can follow the status of omnios issues like this one? So people do not have to ask on the list what the status of bugs/issues are ;-) -- groet, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] software compilation errors
-- Groeten, natxo On Sat, Feb 15, 2014 at 8:55 PM, Tim Rice t...@multitalents.net wrote: On Sat, 15 Feb 2014, Natxo Asenjo wrote: checking the C compiler (cc -fPIC) does not compile code properly *** Error code 1 make: Fatal error: Command failed for target `discount/libmarkdown.a' Can you compile anything on that system? Is pkg://omnios/system/header installed? yes: # pkg info system/header Name: system/header Summary: SunOS Header Files Description: SunOS C/C++ header files for general development of software Category: System/Core State: Installed Publisher: omnios Version: 0.5.11 Build Release: 5.11 Branch: 0.151008 Packaging Date: Wed Dec 4 02:47:08 2013 Size: 12.19 MB FMRI: pkg://omnios/system/header@0.5.11 ,5.11-0.151008:20131204T024708Z ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] software compilation errors
On Sat, Feb 15, 2014 at 11:51 PM, Tim Rice t...@multitalents.net wrote: | On Sat, 15 Feb 2014, Natxo Asenjo wrote: | | checking the C compiler (cc -fPIC) does not compile code properly I should have caught this last time. The OmniOS gcc packages do not provide a cc only gcc. Unless you have the sun compilers installed, there is no cc. Even if they were installed, cc -fPIC is not valid for sun compilers. It would need to be cc -Kpic. You'll need to patch the perl module and build manually. Yes! I installed developer/sunstudio12.1, modified Makefile.PL with your suggestion, installed pkg:/developer/object-file (needed for ar), used gmake instead of make and finally got it to work. Thanks so much for your tip! -- groet, Natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] compiling mediatomb #error non-amd64 code depends on amd64 privileged header!
hi, Tonight I'll try that, I suppose i should look in the Makefile? regards, natxo -- Groeten, natxo On Sun, May 11, 2014 at 11:02 PM, Dan McDonald dan...@omniti.com wrote: Okay. Our headers are 64-bit aware, maybe lose -I/usr/include/amd64 ? Dan Sent from my iPhone (typos, autocorrect, and all) On May 11, 2014, at 3:00 PM, Natxo Asenjo natxo.ase...@gmail.com wrote: hi, trying to use my home omnios server for streaming media I get this error when making mediatomb: g++ -DHAVE_CONFIG_H -I. -I.. -I../tombupnp/upnp/inc-I../src -I../tombupnp/ixml/inc -I../tombupnp/threadutil/inc -I../tombupnp/upnp/inc -I.. -I/usr/local/include-D_REENTRANT -pthreads -I/usr/include/amd64-g -O2 -MT libmediatomb_a-action_request.o -MD -MP -MF .deps/libmediatomb_a-action_request.Tpo -c -o libmediatomb_a-action_request.o `test -f '../src/action_request.cc' || echo './'`../src/action_request.cc In file included from /usr/include/sys/regset.h:420:0, from /usr/include/sys/ucontext.h:36, from /usr/include/sys/signal.h:245, from /usr/include/sys/procset.h:42, from /usr/include/sys/wait.h:43, from /usr/include/stdlib.h:40, from ../src/memory.h:35, from ../src/common.h:36, from ../src/action_request.h:36, from ../src/action_request.cc:36: /usr/include/amd64/sys/privregs.h:42:2: error: #error non-amd64 code depends on amd64 privileged header! #error non-amd64 code depends on amd64 privileged header! ^ make[2]: *** [libmediatomb_a-action_request.o] Error 1 make[2]: Leaving directory `/root/mediatomb-0.12.1/build' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/root/mediatomb-0.12.1' make: *** [all] Error 2 There are quite a few hits on google regarding this #error non-amd64 code depends on amd64 privileged header! on omnios, but so far I could not find a solution. I am building this on a zone with gcc-4.8.1. Any help greatly appreciated. -- Groeten, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] restore zones after crash
hi, the rpool of my home system (on 2 mirrored usb drives ) went first degraded and during the resilver operation the second stick died as well. So no more usb experiments for me, too unreliable and slow to resilver. The plus side of things, restoring the system is very easy, just reinstall omnios and reimport the data pool. But how do I reimport the zones I had? I have the data on the same data pool, but I do not have any config files (obviously, no other backups). I tried recreating the zone manually with the right zonecfg create parameters, but it asks to install before booting. The zone is already installed though in its own file system. I tried creating an empty zone like this with a detached zone: zonecfg:zone1 create -a /tank/zones/zone1 invalid path to detached zone Any tips on how to achieve this? TIA, regards, -- Groeten, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] restore zones after crash
Hi Ian, On Sun, Jun 8, 2014 at 10:30 PM, Ian Collins i...@ianshome.com wrote: Natxo Asenjo wrote: But how do I reimport the zones I had? I have the data on the same data pool, but I do not have any config files (obviously, no other backups). Assuming your zone's root filesystems are intact, have you tried configuring the zones and then attaching them? yes, I tried zonecfg -z zone1 and then zonecfg:zone1 create -a /tank/zones/zone1 invalid path to detached zon If I create the zone normally, it says it is not installed. -- groet, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] restore zones after crash
On Mon, Jun 9, 2014 at 12:04 AM, Ian Collins i...@ianshome.com wrote: Natxo Asenjo wrote: On Sun, Jun 8, 2014 at 11:36 PM, Ian Collins i...@ianshome.com mailto: i...@ianshome.com wrote: No, I was referring to zoneadm -z zone1 attach. Use create -b in the config and then attach once the zone is configured. ok, sorry about that: # zoneadm -z zone1 attach Log File: /var/tmp/zone1.attach_log.W.aOmh ERROR: Failed to locate any dataset mounted at /tank/zones/zone1/root. Attach requires a mounted dataset. Result: Attach Failed. Ah, that old one root@zfstank:~# less /var/tmp/zone1.attach_log.W.aOmh but according to mount, the dataset is mounted, though not in /tank/zones/zone1/root but in /tank/zones/zone1 /tank/zones/zone1 on tank/zones/zone1 read/write/setuid/devices/ nonbmand/exec/xattr/noatime/dev=185001a on Sun Jun 8 15:01:25 2014 Is the zone fubar? Probably not. What is the output of zfs list -r for tank/zones/ zone1? my apologies, I sent it just to you. Here for the list: # zfs list -r tank/zones/zone1 NAME USED AVAIL REFER MOUNTPOINT tank/zones/zone1 13.3G 4.91T 232K /tank/zones/zone1 tank/zones/zone1@r151006 134K - 238K - tank/zones/zone1/ROOT13.3G 4.91T 209K legacy tank/zones/zone1/ROOT@r1510060 - 209K - tank/zones/zone1/ROOT/zbe 116K 4.91T 773M legacy tank/zones/zone1/ROOT/zbe@r1510060 - 773M - tank/zones/zone1/ROOT/zbe-1 11.6K 4.91T 11.1G legacy tank/zones/zone1/ROOT/zbe-1-backup-1 151K 4.91T 11.1G legacy tank/zones/zone1/ROOT/zbe-2 10.3M 4.91T 770M legacy tank/zones/zone1/ROOT/zbe-2@r151006 279K - 12.5G - tank/zones/zone1/ROOT/zbe-3 250K 4.91T 11.1G legacy tank/zones/zone1/ROOT/zbe-4 13.3G 4.91T 11.1G legacy tank/zones/zone1/ROOT/zbe-4@2013-11-09-15:06:18 69.4M - 773M - tank/zones/zone1/ROOT/zbe-4@2013-12-13-10:25:43 17.6M - 12.5G - tank/zones/zone1/ROOT/zbe-4@r151006 186M - 12.7G - tank/zones/zone1/ROOT/zbe-4@2014-01-10-21:17:51 1.35M - 11.1G - tank/zones/zone1/ROOT/zbe-4@2014-02-09-21:12:09 2.75M - 11.1G - tank/zones/zone1/ROOT/zbe-4@2014-04-18-10:36:48 3.13M - 11.1G - tank/zones/zone1/ROOT/zbe-4@2014-06-05-20:10:13 3.00M - 11.1G - tank/zones/zone1/ROOT/zbe-5 215K 4.91T 11.1G legacy -- groet, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] restore zones after crash
On Mon, Jun 9, 2014 at 9:26 AM, Ian Collins i...@ianshome.com wrote: You could try setting the mountpoint of tank/zones/zone1/ROOT/zbe-5 (assuming that was the last version use had mounted) to /tank/zones/zone1/root. zfs set mountpoint=/tank/zones/zone1/root tank/zones/zone1/ROOT/zbe-5 # zfs set mountpoint=/tank/zones/zone1/root tank/zones/zone1/ROOT/zbe-5 cannot set property for 'tank/zones/zone1/ROOT/zbe-5': 'mountpoint' cannot be set on dataset in a non-global zone I found this thread on the OI list: http://openindiana.org/pipermail/openindiana-discuss/2013-July/013297.html and if I read it correctly I miss some stuff in the global zone. O well. I'll probably re-install later today. Thanks for your tips, much appreciated :-) -- groet, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] rpool mirroring alignment problem
On Wed, Jun 11, 2014 at 7:43 PM, Natxo Asenjo natxo.ase...@gmail.com wrote: On Wed, Jun 11, 2014 at 7:32 PM, Dale Ghent da...@omniti.com wrote: On Jun 11, 2014, at 1:01 PM, Natxo Asenjo natxo.ase...@gmail.com wrote: # zpool attach -f rpool c4t13d1s0 c4t14d1s0 cannot attach c4t14d1s0 to c4t13d1s0: devices have different sector alignment Any ideas? Yes, I am aware of the fact both disks are different in size, but provided I am formatting the 2nd one and copying the disklabel from the smaller one it should be ok, shouldn't it? So let’s look at the two drives you’re trying to work with: WD1600BJKT (c4t13d1, your boot disk) WD2500BPVT (c4t14d1, the mirror you want to add) Looking up those drives (WD Scorpio Blue and Scorpio Black models, respectively) shows that the WD2500BPVT has WD’s “Advanced Format” on it - ie, sector size is larger than the traditional 512n which which what the WD1600BJKT has. The Advanced Format is denoted in the drive model number with the “PVT” suffix. Because of this, zfs will refuse to try to meld the drives together into a mirror. You will need to replace the WD2500BPVT with a WD1600BJKT to match your existing one, or at the least make sure the drive is formatted with 512k sectors and not something larger. ok, clear, but the question remains: how do I achieve that (so I do not have a WD1600BJKT, and want to format it with 512k sectors) in omnios? Is it possible or do I just need to reinstall (I do have 2 WD2500BPVT disks, so that is possible; a pain, but possible). using parted both disks seem to start at the same place: # parted /dev/rdsk/c4t13d1p0 unit s print Model: Generic Ide (ide) Disk /dev/rdsk/c4t13d1p0: 312581808s Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End SizeType File system Flags 1 16065s 312576704s 312560640s primary solaris boot # parted /dev/rdsk/c4t14d1p0 unit s print Model: Generic Ide (ide) Disk /dev/rdsk/c4t14d1p0: 488397168s Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End SizeType File system Flags 1 16065s 488392064s 488376000s primary solaris boot ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] rpool mirroring alignment problem
On Wed, Jun 11, 2014 at 8:12 PM, Paul B. Henson hen...@acm.org wrote: On Wed, Jun 11, 2014 at 07:01:01PM +0200, Natxo Asenjo wrote: 1. c4t13d1 ATA-WDCWD1600BJKT-7-1A11 cyl 19454 alt 2 hd 255 sec 63 /pci@0,0/pci1022,9603@2/pci1014,3b1@0/sd@d,1 2. c4t14d1 ATA-WDCWD2500BPVT-0-1A01 cyl 30398 alt 2 hd 255 sec 63 /pci@0,0/pci1022,9603@2/pci1014,3b1@0/sd@e,1 [...] # zpool attach -f rpool c4t13d1s0 c4t14d1s0 cannot attach c4t14d1s0 to c4t13d1s0: devices have different sector alignment Any ideas? Looks like the WD2500BPVT has Advanced Format Technology, ie 4k sectors: http://www.newegg.com/Product/Product.aspx?Item=N82E16822136565 Whereas the WD1600BJKT is a classic 512 byte sector device. You can't currently add a 4k sector drive to a vdev using 512 byte sectors. Any chance you could do the initial install to the 4k device, and then add the 512 byte device as the second half of the mirror? I think that would work. Or you could trick the OS into thinking the 512 byte device actually has 4k sectors... http://blog.delphix.com/gwilson/2012/11/15/4k-sectors-and-zfs/ thanks for the info. I think I will reinstall to the WD2500BPVT after a quick read of both your link and Dale's ... -- regards, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] trouble building DBD::mysql (perl)
hi, I have installed built perl 5.20 using perlbrew and gcc-4.8.1. # perl -v This is perl 5, version 20, subversion 0 (v5.20.0) built for i86pc-solaris-thread-multi- 64int I am using database/mysql-56 from the uulm.mawi repository, which keeps its libraries/include files in /usr/local/mysql/5.6/{lib/include} . For an application (RT) I want to use the mysql driver and I tried installing it throuch cpanm. Then cpanm failed because it could not find the path to mysql_config. No problem, I can set it: = # perl Makefile.PL --mysql_config=/usr/local/mysql/5.6/bin/mysql_config --cflags=-m32 PLEASE NOTE: For 'make test' to run properly, you must ensure that the database user '' can connect to your MySQL server and has the proper privileges that these tests require such as 'drop table', 'create table', 'drop procedure', 'create procedure' as well as others. mysql grant all privileges on test.* to ''@'localhost' identified by 's3kr1t'; You can also optionally set the user to run 'make test' with: perl Makefile.PL --testuser=username I will use the following settings for compiling and testing: cflags(User's choice) = -m32 embedded (mysql_config ) = ldflags (mysql_config ) = -R/usr/local/mysql/5.6/lib libs (mysql_config ) = -L/usr/local/mysql/5.6/lib -lmysqlclient -lsocket -lnsl -lm -lssl -lcrypto mysql_config (Users choice ) = /usr/local/mysql/5.6/bin/mysql_config nocatchstderr (default ) = 0 nofoundrows (default ) = 0 ssl (guessed ) = 1 testdb(default ) = test testhost (default ) = testpassword (default ) = testport (default ) = testsocket(default ) = testuser (guessed ) = To change these settings, see 'perl Makefile.PL --help' and 'perldoc DBD::mysql::INSTALL'. Using DBI 1.631 (for perl 5.02 on i86pc-solaris-thread-multi-64int) installed in /opt/perl5//perls/perl-5.20.0/lib/site_perl/5.20.0/i86pc-solaris-thread-multi-64int/auto/DBI/ Generating a Unix-style Makefile Writing Makefile for DBD::mysql Writing MYMETA.yml and MYMETA.json = But then make fails: === # make Skip blib/lib/DBD/mysql/INSTALL.pod (unchanged) Skip blib/lib/DBD/mysql.pm (unchanged) Skip blib/lib/Bundle/DBD/mysql.pm (unchanged) Skip blib/lib/DBD/README.pod (unchanged) Skip blib/lib/DBD/mysql/GetInfo.pm (unchanged) Running Mkbootstrap for DBD::mysql () chmod 644 mysql.bs gcc -c -I/opt/perl5/perls/perl-5.20.0/lib/site_perl/5.20.0/i86pc-solaris-thread-multi-64int/auto/DBI -m32 -DDBD_MYSQL_WITH_SSL -DDBD_MYSQL_INSERT_ID_IS_GOOD -g -D_REENTRANT -DPTR_IS_LONG -fno-stack-protector -fwrapv -fno-strict-aliasing -pipe -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DPERL_USE_SAFE_PUTENV -O -DVERSION=\4.027\ -DXS_VERSION=\4.027\ -fPIC -I/opt/perl5/perls/perl-5.20.0/lib/5.20.0/i86pc-solaris-thread-multi-64int/CORE dbdimp.c In file included from dbdimp.c:20:0: dbdimp.h:21:49: fatal error: mysql.h: No such file or directory #include mysql.h /* Comes with MySQL-devel */ ^ compilation terminated. make: *** [dbdimp.o] Error 1 = so it cannot find the header. But it is there, this is what mysql_config tells me: # ./mysql_config Usage: ./mysql_config [OPTIONS] Options: --cflags [-I/usr/local/mysql/5.6/ include -m64 -fPIC -g -fabi-version=2 -fno-omit-frame-pointer -fno-strict-aliasing] --cxxflags [-I/usr/local/mysql/5.6/include -m64 -fPIC -g -fabi-version=2 -fno-omit-frame-pointer -fno-strict-aliasing] --include[-I/usr/local/mysql/5.6/include] --libs [-L/usr/local/mysql/5.6/lib -R/usr/local/mysql/5.6/lib -lmysqlclient -lsocket -lnsl -lm -lssl -lcrypto] --libs_r [-L/usr/local/mysql/5.6/lib -R/usr/local/mysql/5.6/lib -lmysqlclient_r -lsocket -lnsl -lm -lssl -lcrypto] --plugindir [/usr/local/mysql/5.6/lib/plugin] --socket [/var/mysql/5.6/run/mysqld.socket] --port [0] --version[5.6.17] --libmysqld-libs [-L/usr/local/mysql/5.6/lib -R/usr/local/mysql/5.6/lib -lmysqld -lnsl -lm -lssl -lcrypto -lsocket] --variable=VAR VAR is one of: pkgincludedir [/usr/local/mysql/5.6/include] pkglibdir [/usr/local/mysql/5.6/lib] plugindir [/usr/local/mysql/5.6/lib/plugin] And if I look in the include dir, sure there it is: root@zone1:/usr/local/mysql/5.6/bin# ls -l ../include/mysql.h -rw-r--r-- 1 root bin 29058 Jun 15 16:56 ../include/mysql.h Not really sure how to build this. Any tips greatly appreciated. Thanks. -- Groeten, natxo
Re: [OmniOS-discuss] trouble building DBD::mysql (perl)
Hi John, On Mon, Jun 16, 2014 at 7:57 PM, John D Groenveld jdg...@elvis.arl.psu.edu wrote: In message cahbejzxp2e+ubav6forfsdmiuk_f1ahn8bvf9py1qokzdv5...@mail.gmail.com , Natxo Asenjo writes: # perl Makefile.PL --mysql_config=/usr/local/mysql/5.6/bin/mysql_config --cflags=-m32 [snipped] I will use the following settings for compiling and testing: cflags(User's choice) = -m32 My WAG is that your --cflags is overriding mysql_config --cflags. Remove yours. yes, I thought that at first, but I need that because otherwise I get this: ld: fatal: file dbdimp.o: wrong ELF class: ELFCLASS64 ld: fatal: file processing errors. No output written to blib/arch/auto/DBD/mysql/mysql.so because: # /usr/local/mysql/5.6/bin/mysql_config --cflags -I/usr/local/mysql/5.6/include -m64 -fPIC -g -fabi-version=2 -fno-omit-frame-pointer -fno-strict-aliasing Happy hacking, I try to ;-) Thanks, -- groet, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] trouble building DBD::mysql (perl)
Hi Dan, On Mon, Jun 16, 2014 at 7:53 PM, Dan McDonald dan...@omniti.com wrote: On Jun 16, 2014, at 1:39 PM, Natxo Asenjo natxo.ase...@gmail.com wrote: gcc -c -I/opt/perl5/perls/perl-5.20.0/lib/site_perl/5.20.0/i86pc-solaris-thread-multi-64int/auto/DBI -m32 -DDBD_MYSQL_WITH_SSL -DDBD_MYSQL_INSERT_ID_IS_GOOD -g -D_REENTRANT -DPTR_IS_LONG -fno-stack-protector -fwrapv -fno-strict-aliasing -pipe -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DPERL_USE_SAFE_PUTENV -O -DVERSION=\4.027\ -DXS_VERSION=\4.027\ -fPIC -I/opt/perl5/perls/perl-5.20.0/lib/5.20.0/i86pc-solaris-thread-multi-64int/CORE dbdimp.c In file included from dbdimp.c:20:0: dbdimp.h:21:49: fatal error: mysql.h: No such file or directory #include mysql.h /* Comes with MySQL-devel */ I don't see a -I in this gcc path that would point you at where mysql.h lives. You said earlier: I am using database/mysql-56 from the uulm.mawi repository, which keeps its libraries/include files in /usr/local/mysql/5.6/{lib/include} . I don't see -I /usr/local/mysql/5.6/include in your gcc arguments above. absolutely right. For what it's worth, I could set the include path in the --cflags like this perl Makefile.PL --cflags=-I/usr/local/mysql/5.6/include -m32 -fPIC -g -fabi-version=2 -fno-omit-frame-pointer -fno-strict-aliasing but then one of the shared libraries of the mysql package was only 64 bits, so it failed again. So now I tried with the system perl and it worked ;-) Thanks for the inputs. -- regards, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] trouble building DBD::mysql (perl)
hi John, On Mon, Jun 16, 2014 at 10:16 PM, John D Groenveld jdg...@elvis.arl.psu.edu wrote: In message cahbejzx7hyzdseofnzpyob9l+e0rh3y37suvtgzd+coyp0o...@mail.gmail.com , Natxo Asenjo writes: bits, so it failed again. So now I tried with the system perl and it worked ;-) RT's make testdeps lists a fairly large footprint; I think you're better off proceeding down the custom Perl (and Apache 2.2) path you started on as you're less likely to break an OmniOS system application with cpan(1) and pkg update is less likely to break RT. yes, it certainly uses a fair bit of cpan. You are probably right because of the KYSTY principle, of course. -- regards, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] trouble building DBD::mysql (perl)
hi, following on this saga, with perlbrew I got it installed but: # perl -MDBD::mysql -e 1 Can't load '/opt/perl5//perls/perl-5.20.0/lib/site_perl/5.20.0/i86pc-solaris-thread-multi-64/auto/DBD/mysql/mysql.so' for module DBD::mysql: ld.so.1: perl: fatal: relocation error: file /usr/local/mysql/5.6/lib/libmysqlclient.so.18: symbol __gxx_personality_v0: referenced symbol not found at /opt/perl5//perls/perl-5.20.0/lib/5.20.0/i86pc-solaris-thread-multi-64/DynaLoader.pm line 193. at -e line 0. Compilation failed in require. BEGIN failed--compilation aborted. Does this ring a bell, anyone? Thanks! -- groet, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] trouble building DBD::mysql (perl)
On Tue, Jun 17, 2014 at 8:17 PM, Natxo Asenjo natxo.ase...@gmail.com wrote: hi, following on this saga, with perlbrew I got it installed but: # perl -MDBD::mysql -e 1 Can't load '/opt/perl5//perls/perl-5.20.0/lib/site_perl/5.20.0/i86pc-solaris-thread-multi-64/auto/DBD/mysql/mysql.so' for module DBD::mysql: ld.so.1: perl: fatal: relocation error: file /usr/local/mysql/5.6/lib/libmysqlclient.so.18: symbol __gxx_personality_v0: referenced symbol not found at /opt/perl5//perls/perl-5.20.0/lib/5.20.0/i86pc-solaris-thread-multi-64/DynaLoader.pm line 193. at -e line 0. Compilation failed in require. BEGIN failed--compilation aborted. I have this other problem when using the system perl and the mysql-55 package from ms.omniti (it builds and compiles ok, though): # perl -MDBD::mysql Can't load '/usr/perl5/site_perl/5.16.1/i86pc-solaris-thread-multi-64int/auto/DBD/mysql/mysql.so' for module DBD::mysql: ld.so.1: perl: fatal: /usr/perl5/site_perl/5.16.1/i86pc-solaris-thread-multi-64int/auto/DBD/mysql/mysql.so: wrong ELF class: ELFCLASS64 at /usr/perl5/5.16.1/lib/i86pc-solaris-thread-multi-64int/DynaLoader.pm line 190. at - line 0. Is there a 64bit system perl? I do not see it in /usr/bin/amd64/perl like for python2.6. Thanks! -- groet, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Help setting up a boot server
On Tue, Jun 24, 2014 at 10:44 AM, Michael Mounteney gat...@landcroft.co.uk wrote: Hello, I would appreciate some advice in setting-up a boot server. This would have OmniOS as the server and a couple of diskless HP thin clients running Linux as the clients. The Linux kernel is already configured as a diskless NFS root client but it is currently loaded from a small partition on the thin client's flash ROM. I'd like to move it entirely onto the server. As I understand it, the server must run a TFTP server and as that communicates via UDP/IP, a DHCP server is also required. Presumably the best thing is to configure the DHCP server to serve a fixed IP address to the client's MAC address, so that the Linux kernel can also use DHCP to get the (same) IP address. Currently, the IP address is set in the arguments passed to the kernel. https://wiki.gentoo.org/wiki/Diskless_nodes#About_Etherboot says that the served-up client kernel must be prepared with etherboot. So a few random musings. Any thoughts ? Best server-side software ? where there's a choice. all the pieces are there I think. Recently the isc-dhcp server got into the packages if I remember correctly and there is a tftp package as well.. If you want fixed ip addresses you can achieve that using reservations in dhcp. The rest is pretty trivial. My notes for configuring the tftp service in omnios: pkg install tftp echo tftp dgram udp wait root /usr/sbin/in.tftpd in.tftpd -s /tftpboot /tmp/tftp.inetd svcadm enable inetd inetconv -i /tmp/tftp.inetd -o /tmp svccfg import /tmp/tftp-udp.xml svcadm restart tftp/udp will give you a working tftp service with the tftp root in /tftpboot. I have never used etherboot and doubt that you need it, but you should know that better ;-) And lastly you will need an nfs share for the diskless clients, but that is pretty simple as well. -- groet, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] vnic zone disabled after reboot
hi, according to this doc: http://docs.oracle.com/cd/E19455-01/806-5529/6jehkcs2t/index.html I have create a /etc/dhcp.interface (vnic1) file. Then rebooted and I have link, but things are a bit strange: # ipadm show-addr ADDROBJ TYPE STATEADDR lo0/v4static ok 127.0.0.1/8 vnic1/? dhcp ok 192.168.0.171/24 lo0/v6static ok ::1/128 vnic1/v4 dhcp disabled ? So I deleted the vnic1 interface, recreated it with just ipadm create-if vnic1 and rebooted with the /etc/dhcp.interface file and now it works: # ipadm show-addr ADDROBJ TYPE STATEADDR lo0/v4static ok 127.0.0.1/8 vnic1/? dhcp ok 192.168.0.171/24 lo0/v6static ok ::1/128 Is this the right way to do it? -- groet, Natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] centos 7 nfsv4 client nobody problems
hi, probably something easy, but I cannot seem to solve it. I have shared using nfs a dataset with these properties on omnios: # zfs get sharenfs tank/nuc01 NAMEPROPERTY VALUE SOURCE tank/nuc01 sharenfs rw=@192.168.0.0.0/24,root=@192.168.0.0/24 local so quite liberal you should think ;-) But my centos 7 client always squashes the root files: # ls -l nuc01/ -rw---. 1 nobody nobody 8591507456 Oct 1 22:43 kdc.qcow2 -rw-r--r--. 1 nobody nobody 0 Oct 2 19:38 test and these are the mount options: (rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.0.11,local_lock=none,addr=192.168.0.172) I have modified /etc/idmapd.conf on the centos host to have the same Domain as the omnios box. Is nfsv3 my only option? Thanks! -- Groeten, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] centos 7 nfsv4 client nobody problems
On Thu, Oct 2, 2014 at 7:46 PM, Natxo Asenjo natxo.ase...@gmail.com wrote: and of course it was every rh admin best friend: selinux # setsebool -P virt_use_nfs on and everything will be fine if you want to use nfs for libvirtd or just turn it off ;-) Sorry for the noise. ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] best guide to tftp ?
On Fri, Oct 24, 2014 at 10:53 PM, Michael Mounteney gat...@landcroft.co.uk wrote: Hello, I want to use OmniOS as a boot server for various Linux thin clients. What's the most appropriate guide out there? There's a few, referring to obsolete problems, other OSs etc. Just tested and it works. Searching for in.tftpd # pkg search in.tftpd INDEX ACTION VALUE PACKAGE basename file usr/sbin/in.tftpd pkg:/service/network/tftp@0.5.11-0.151012 # pkg publisher PUBLISHER TYPE STATUS URI omniosorigin online http://pkg.omniti.com/omnios/r151012/ So you should just install the tftp package in the omnios publisher and then activate the tftp service by editing inetd.conf and adding the line: tftpdgram udp6waitroot/usr/sbin/in.tftpd in.tftpd -s /tftpboot and then running the inetconv command. This will create an SMF service, network/tftp/udp6. Create a /tftpboot dir in your omnios host and there you go. Edit the pxe files like you are used to. -- Groeten, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] KVM within a child zone
On Tue, Dec 23, 2014 at 10:44 AM, Lauri Tirkkonen loth...@iki.fi wrote: On Tue, Dec 23 2014 19:28:47 +1000, Michael Mounteney wrote: That gets it a bit closer but I still need the real interface (e1000g1) for vnc and sshing in etc. and I can't give that to the zone exclusively. You can create a vnic over your physical interface (with dladm(1M)) and then give that to the zone. my thoghts exactly. This is what I do in such cases: First let's see the real network hardware: # dladm show-phys LINK MEDIASTATE SPEED DUPLEXDEVICE bge0 Ethernet up 1000 full bge0 then create a vnic on top of that # dladm create-vnic -l bge0 vnic1 check it's there: # dladm show-vnic LINK OVER SPEED MACADDRESSMACADDRTYPE VID vnic1bge0 1000 2:8:20:ae:f6:c0 random 0 create a zone and assign it the new vnic: global # zonecfg -z sapacc sapacc: No such zone configured Use 'create' to begin configuring a new zone. zonecfg:sapacc create zonecfg:sapacc set zonepath=/export/zones/sapacc zonecfg:sapacc set autoboot=false zonecfg:sapacc set ip-type=exclusive zonecfg:sapacc add net zonecfg:sapacc:net set physical=vnic1 zonecfg:sapacc:net end zonecfg:sapacc verify zonecfg:sapacc commit zonecfg:sapacc exit And then configure the vnic inside the zone like you would normally -- Groeten, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Issues about OmniOS software installation package
hi, On Mon, Apr 27, 2015 at 7:14 AM, Nan Xiao xiaonan830...@gmail.com wrote: Hi Dan, I have installed the omniOS on vagrant. For some reasons, I can't configure OS to visit the internet, so let's why I want to get some out-of-box *.pkgs like Solaris. do you have defined what your default gateway is? http://omnios.omniti.com/wiki.php/GeneralAdministration -- regards, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] import zpool in freebsd/linux
hi, for reasons not relevant for a discussion here I need to move the data on on a on omnios zpool to a linux (preferably) ZoL installation or to freebsd (second choice). This is a data zpool, not rpool. So would it work to install another OS on the disks allocated to the rpool and then importing the data zpool? Or do I need to make a data migration copying stuff around with extra hardware? Thanks for any inputs on this matter. -- Groeten, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] OmniOS as home serwer (NAT, private projects)
hi Krzysztof, On Sun, Jun 12, 2016 at 11:35 AM, Krzysztof Grzempawrote: > Cheers guys, > > I'm planning to build my own server at home for multiple purposes (my > projects, home NAS etc). I'm planning to use zones to separate WAN access > server (www hosting, git and svn repos, email maybe..) and SAN > functionalities for LAN only access. > Now, i'm huge fan of Illumos. I used to work with Solaris 8 to 11, and i > really enjoy it. I wish to use ZFS as the best storage solution, but what > concern me most is availability of technologies that i'm going to use. For > WAN purposes I need apache2, php5, mariadb, python (at least 2.7),git, svn, > and maybe fish shell ;) . For my NAS, I need samba, nfs, ftp, DLNA > [mediatomb, serviio] (sharing video to TV directly). > AFAIK and read on the net, probably every of those technologies are doable > on OmniOS, but the problem is time spent on installing, solving problems > etc. > Of course, there is always the linux solution, but i would like not go > there as Illumos has may better storage (ZFS on linux sucks IHMO) > Has anyone got expierience in setting up such stack on OmniOS? (or any > other Illumos distro?) Problems? Advices? > > I run a microserver at home that does NFS/cifs, dlna (serviio in the past, pldna now), I use crashplan for backups to the cloud. I use it for testing stuff in zones a lot as well with the stacks you mention and others. I don't use samba, the cifs server is very reliable and easy to use, and now we have smb2 in it. I don't use ftp either, so I cannot comment on that, although I vaguely remember talk about removing it because it was removed from illumos. The only thing I cannot do is kvm because that is not available for amd cpus, but that is not really a big deal. I got a nuc from work to use it as hypervisor (esx/kvm) and use the omnios box as storage datastore for the vms. Works great too. Not much to say, it works very well, updates/upgrades are easy and work. An omnios box is a great home server. But if you are not willing to spend some time learning how things work in solaris/illumos then maybe the linux solution is better suited for you. It is a different system after all, lots of things are similar but others differ. HTH, -- Groeten, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] smb 2 omnios OmniOS r151016
hi, in another thread (.$EXTEND/$QUOTA) I read that smb v2 is enabled (yay!). Do we need to do something to use that or it will "just work"? Thanks! -- Groeten, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] smb 2 omnios OmniOS r151016
by the way, I cannot see anything regarding smb/cifs 2 in http://omnios.omniti.com/wiki.php/ReleaseNotes/r151016 ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] SMB issues after r151014 -> r151018
On Fri, Apr 22, 2016 at 3:53 AM, Gordon Rosswrote: > I'm not sure how anyone ever gets access when your ACL has this ACE: > everyone@:rwxpdDaARWcCos:fd-:deny excellent catch! Deny ace's always get processed first in cifs, how could I miss that ;-) -- regards, Natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] SMB issues after r151014 -> r151018
Hi Olaf On Thu, Apr 21, 2016 at 8:31 PM, Olaf Marzocchiwrote: > Thanks for the help. > Well first of all, how can the SMB server require everyone to have > read/execute access? no more private shares? > > Anyway, I got it working (for now) with: > > drwxr-xr-x+ 16 olaf olaf 16 Apr 21 20:25 olaf > user:olaf:rwxpdDaARWcCos:fd-:allow >group:2147483648:rwxpdDaARWcCos:fd-:allow > everyone@:r-x---a-R-c--s:---:allow > everyone@:rwxpdDaARWcCos:fd-:deny > > Still, why am I able to access without issues another share that has > (basically) the same permissions as I had on my folder? > > d-S---+ 27 root temps170 Apr 20 23:10 Temporary > user:olaf:rwxpdDaARWcCos:fd-:allow >group:2147483648:rwxpdDaARWcCos:fd-:allow > user:transmis:--x---a-R-c--s:---:allow > everyone@:rwxpdDaARWcCos:fd-:deny > > I am member of group "temps" too. > This seems strange to me... it doesn't make sense. > > It is working now, but any explanation? I don't like to have everyone rx > permissions on my private folder, even if the ACLs will not propagate said > permissions to its contents. > I do not know exactly what has changed but I can tell you private shares still work. This share is only accessible for one one user: root@zfstank:/root# /usr/bin/ls -Vd /tank/fotos/ d-+311 root root 322 Mar 11 14:00 /tank/fotos/ user:username:rwxpdDaARWcCos:fd-:allow root@zfstank:/root# ls -ld /tank/fotos/ d-+ 311 root root 322 Mar 11 14:00 /tank/fotos/ I do not remember exactly when I set it up, but it has been working at least since version 151014 HTH, -- regards, Natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] cifs anonymous troubles
hi, trying to set up an anonymous share on workgroup mode I do not get it working. I have a dataset tank/test with these sharesmb properties: zfs get sharesmb tank/testshare NAMEPROPERTY VALUE SOURCE tank/testshare sharesmb name=test,guestok=true local These are the permissions on that path: # /usr/bin/ls -Vd /tank/testshare/ drwxrwxrwx+ 14 root root 14 Sep 11 2015 /tank/testshare/ everyone@:rwxpdDaARWcCos:fd-:allow Both using a windows client (win 2012r2) as a linux smbclient (fedora 23), both quite modern, I cannot access the share: Linux smbclient: $ smbclient -U " " -L //192.168.0.172 -N Anonymous login successful Domain=[WORKGROUP] OS=[SunOS 5.11 omnios-r151018-ae314] Server=[Native SMB service] Sharename Type Comment - --- c$ Disk Default Share testDisk Connection to 192.168.0.172 failed (Error NT_STATUS_CONNECTION_REFUSED) NetBIOS over TCP disabled -- no workgroup available Windows client: C:\Users\Administrator>net view \\192.168.0.172 System error 5 has occurred. Access is denied. Using a local user works, with smb2 ;-) Any one success with guestok=true and cifs? -- Groeten, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] cifs anonymous troubles
hi Gordon, On Sun, Apr 17, 2016 at 5:38 PM, Gordon Rosswrote: > Hi Dan, > > So with that bug fixed, one can logon as "guest" only if: > (1) you actually ask for guest in your logon request, > (2) a local Unix account named "guest" exists, and > (3) the guest account is enabled for SMB > > Therefore, if you were using guest access before 1122 was fixed, > (and were depending on accidental guest access working), > you'll need to do the following to re-enable guest access: > > useradd (options] guest > smbadm enable-user guest I confirm this works. Thanks! ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] OmniOS r151018 is now out!
On Thu, Apr 14, 2016 at 8:47 PM, Dan McDonaldwrote: > Start with the release notes: > > http://omnios.omniti.com/wiki.php/ReleaseNotes/r151018 > home box upgraded, zero problems ;-) Thanks! ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Low powered and cheap OmniOS server?
hi, On Thu, Sep 29, 2016 at 4:54 PM, Paul Jochumwrote: > Hi All: > > Looking for the latest recommendations on a low powered and cheap > OmniOS server. This would be for home use, looking to use it as way of > backing up Linux and Windows boxes. Anyone have a recommendation? > HP microserver 40NL, with a IBM serveraid m1015 sas/sata raid controller in jbod mode. I use the internal 4 sata 2 connectors with 4x3Tib hard drives, and I bought one of these (not available any more, unfortunately): https://azerty.nl/0-1651-403300/sharkoon-sata-quickport-intern-6-bay-.html I replaced the cd/dvd drive with that bay expansion, I have 2 laptop drives as rpool and one ssd as cache. If I run out of space I can add 3 2,5'' hard drives to the pool, or create a new pool. It even has a e-sata connection, so I could add an external enclosure as well. I got the kvm module as well, so it's quite a convenient litlle thing. Not the fastest cpu, but hey, for that price and low consumption .. ;-) -- Groeten, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] plex on lx zone (centos 6.8) stops working after 2/3 days
hi, the subject says it. I installed a centos lx zone following the fine manual (https://omnios.omniti.com/wiki.php/LXZones) and it works great, but plex disappears from the network every 2 to three days. Rebooting the zone solves the problem until it happens again. How could I troubleshoot this issue? The zone os is available (I can login using ssh, so networking works, only plex does not broadcast). TIA -- Groeten, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] cifs smb 2.1 errors when using windows 10 backup tool
hi, There is a w10 system at the home and it's a bit critical for the wife ;-), so I want to have this up and running asap if some kind of trouble happens with it. Anyway, this windows 10 OS has a backup tool that allows you to dump an image to a network share using cifs, obviously. So I have a zfs file system, shared it for cifs, set the permissions for the share. Start the backup, and it will fail consistently when it has reached 57%. After much searching, I found this: https://social.technet.microsoft.com/Forums/windows/en-US/c2032e37-ebe9-4221-9d37-5525fcdaae19/windows-8-backup-win7-file-recovery-system-image-creation-to-nas-device-fails-with-error?forum=w8itprogeneral And yes, after: # sharectl set -p max_protocol=1 smb and restarting the cifs service, now the backup is running correctly (97% and counting). Apparently it has to do with 'resilency support', whatever that may be: https://support.microsoft.com/en-us/kb/2920193 Which is a shame, because now the cifs host is limited to smb 1.5 instead of 2.1 (but at least it works). Hopefully I spare somebody some unnecessary pain with this info. And it would be awesome if this 'resiliciency support' made it to the cifs server in a next version ;-) Thanks! -- Groeten, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] cifs smb 2.1 errors when using windows 10 backup tool
On Wed, Oct 12, 2016 at 5:00 PM, Jeff Stockettwrote: > FWIW, you could create a backup volume and share it via iscsi to your > wife’s PC – quite a few commands to accomplish on the omnios side but easy > if you have nappit already. Once you attach it, run windows backup, and it > will immediately see it as an available backup location and initialize it > for just that purpose if you let it. Then you could leave your CIFS shares > 2.1. > sure, you can offer an iscsi disk but recovering bare metal from iscsi targets is not as easy as from a share ;-) and well, as I read in the thread, Nexenta already has this and will upstream their work (thanks! awesome work), so for the time being I guess I can either turn smb 1 on/off every now and then for a backup, or just live with a slower cifs protocol. -- Groeten, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] cifs smb 2.1 errors when using windows 10 backup tool
hi, > > On Wed, Oct 12, 2016 at 6:07 PM, Gordon Ross> wrote: > >> Interesting finding re. VHD support needing resiliency support in SMB 2.1. >> Thanks for the KB article: https://support.microsoft.com/en-us/kb/2920193 >> >> We have resiliency support in NexentaStor 5.0 (shameless plug:) >> https://nexenta.com/products/nexentastor >> We should work on upstreaming that code soon. >> > That would be terrific! Thanks for your efforts for making an awesome cifs service. -- Groeten, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] cifs smb 2.1 errors when using windows 10 backup tool
On Wed, Oct 12, 2016 at 6:07 PM, Gordon Ross <gordon.w.r...@gmail.com> wrote: > Interesting finding re. VHD support needing resiliency support in SMB 2.1. > Thanks for the KB article: https://support.microsoft.com/en-us/kb/2920193 > > We have resiliency support in NexentaStor 5.0 (shameless plug:) > https://nexenta.com/products/nexentastor > We should work on upstreaming that code soon. > > > On Wed, Oct 12, 2016 at 8:54 AM, Natxo Asenjo <natxo.ase...@gmail.com> > wrote: > > hi, > > > > There is a w10 system at the home and it's a bit critical for the wife > ;-), > > so I want to have this up and running asap if some kind of trouble > happens > > with it. > > > > Anyway, this windows 10 OS has a backup tool that allows you to dump an > > image to a network share using cifs, obviously. > > > > So I have a zfs file system, shared it for cifs, set the permissions for > the > > share. Start the backup, and it will fail consistently when it has > reached > > 57%. > > > > After much searching, I found this: > > https://social.technet.microsoft.com/Forums/windows/ > en-US/c2032e37-ebe9-4221-9d37-5525fcdaae19/windows-8-backup- > win7-file-recovery-system-image-creation-to-nas-device- > fails-with-error?forum=w8itprogeneral > > > > And yes, after: > > > > # sharectl set -p max_protocol=1 smb > > > > and restarting the cifs service, now the backup is running correctly (97% > > and counting). > > > > Apparently it has to do with 'resilency support', whatever that may be: > > > > https://support.microsoft.com/en-us/kb/2920193 > > > > Which is a shame, because now the cifs host is limited to smb 1.5 > instead of > > 2.1 (but at least it works). > > > > Hopefully I spare somebody some unnecessary pain with this info. And it > > would be awesome if this 'resiliciency support' made it to the cifs > server > > in a next version ;-) > > > > Thanks! > > > > -- > > Groeten, > > natxo > > > > ___ > > OmniOS-discuss mailing list > > OmniOS-discuss@lists.omniti.com > > http://lists.omniti.com/mailman/listinfo/omnios-discuss > > > -- -- Groeten, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] LX Zone DTrace
hi, On Sat, Jan 14, 2017 at 3:16 PM, Mini Traderwrote: > Well the author at my request was able to remove the call to os.getcwd() > which allows the program to operate. > > > If anyone wants to tinker here is an example that will likely break on > someones system. I don't know if this is an LX bug, libc bug, python bug > etc. > > # read a directory, stat all files > > import os > import sys > from stat import * > > def chdir(d): > global cwdlist > > if d != '.': > os.chdir(d) > if d == '..': > cwdlist.pop() > else: > cwdlist.append(d) > print repr('/'.join(cwdlist)) > # Comment the line below to allow things to run > os.getcwd() > > def walk(d): > chdir(d) > dirlist = os.listdir('.') > dirlist.sort() > for f in dirlist: > try: > s = os.lstat(f) > if S_ISDIR(s.st_mode): > walk(f) > except OSError, err: > print err > chdir('..') > > if len(sys.argv) != 2: > print 'need 1 arg, directory to scan' > > os.chdir(sys.argv[1]) > cwd = os.getcwd() > cwdlist = cwd.split('/') > > walk('.') > > runs fine in a centos 6.8 container, no problem. I even have a couple of mount points with several thousand files and it walks everything without a hitch. -- regards, Natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] plex on lx zone (centos 6.8) stops working after 2/3 days
On Mon, Nov 28, 2016 at 3:51 PM, Rafael Pardinaswrote: > Perhaps you should add a network mask to avoid network inconsistencies. I > did it by just adding the IP using the CIDR notation, in your case it > should be: > > add property (name=ips,value="192.168.0.120/24") <-- or whatever your > subnet definition may be. > I added the netmask and restarted the zone. 4 days later I can still use it :-) So I guess this has fixed it. Thanks! -- regards, Natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] NFS 4.2 Support - Sparse Files
On Thu, Jan 5, 2017 at 3:56 PM, Olaf Marzocchiwrote: > I'm using right now Crashplan under OmniOS but it's been already declared > as discontinued and I may need an alternative sometimes in the future, even > if it still works fine. > same here, althouth since the lx zones I think I will just install a linux container with the crashplan software and backup zfs nfs volumes. As it all works in the same box, there should not be any performance hit. So not a problem anymore in my opinion, thankfully. -- regards, Natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] How some services boot
hi, On Thu, Apr 6, 2017 at 8:16 PM, Software Information < softwareinfor...@gmail.com> wrote: > Hi All > Just trying to understand how some services work under OmniOS. Please help > me to understand this. I have build omnios-r151020-4151d05 and I am running > a Git Server in a zone. I used packages to install Git with a pkg install. > When I run svcs, I don't see the git service at all but I can use a client > to connect to it and the port is open. I am trying to get better at service > management. Where can I find the script that is starting this service. > There is no 'official' git server. You can review the methods of using a bare repo specified in https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols (chapter 4 of the excellent - and free to read - git book). If what you are looking for are free alternatives to github, you could take a look at gitlab, gitbucket, gitprep (just look them up in your favorite search engine). There are obviously non-free (but excellent) alternatives as bitbucket. You can also take a look at gitolite, but it has no web frontend, it is purely an access control git shell. -- Groeten, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] crash after upgrading to 151024
hi, I upgraded our home nas from the old stable ce to the new stable one. The process went ok, but after rebooting it has crashed twice: this is the info I can see with fmpdump: # fmdump -Vp -u 95f72642-1099-ca7a-f1ca-952f0f5a9906 TIME UUID SUNW-MSG-ID Nov 19 2017 18:01:08.485243000 95f72642-1099-ca7a-f1ca-952f0f5a9906 SUNOS-8000-KL TIME CLASS ENA Nov 19 18:01:08.3130 ireport.os.sunos.panic.dump_available 0x Nov 19 18:00:19.3332 ireport.os.sunos.panic.dump_pending_on_device 0x nvlist version: 0 version = 0x0 class = list.suspect uuid = 95f72642-1099-ca7a-f1ca-952f0f5a9906 code = SUNOS-8000-KL diag-time = 150868 390045 de = fmd:///module/software-diagnosis fault-list-sz = 0x1 fault-list = (array of embedded nvlists) (start fault-list[0]) nvlist version: 0 version = 0x0 class = defect.sunos.kernel.panic certainty = 0x64 asru = sw:///:path=/var/crash/unknown/.95f72642-1099-ca7a-f1ca-952f0f5a9906 resource = sw:///:path=/var/crash/unknown/.95f72642-1099-ca7a-f1ca-952f0f5a9906 savecore-succcess = 1 dump-dir = /var/crash/unknown dump-files = vmdump.1 os-instance-uuid = 95f72642-1099-ca7a-f1ca-952f0f5a9906 panicstr = BAD TRAP: type=e (#pf Page fault) rp=ff0016065cc0 addr=0 occurred in module "unix" due to a NULL pointer dereference panicstack = unix:die+df () | unix:trap+e08 () | unix:_cmntrap+e6 () | unix:strncpy+28 () | lx_brand:lx_prctl+48a () | lx_brand:lx_syscall_enter+16f () | unix:brand_sys_syscall+1bd () | crashtime = 150541 panic-time = Sun Nov 19 17:55:41 2017 CET (end fault-list[0]) fault-status = 0x1 severity = Major __ttl = 0x1 __tod = 0x5a11b8d4 0x1cec3878 The first time it crashed after re-attaching a ipkg zone, and the second time after I started a vmware vm hosted in a nfs share on the omnios host. I have the dumped crash files, I do not know if anyone could take a look at them. This is a microserver HP proliant N40L, and has been rock stable for 4 years, so maybe the hardware is at fault, obviously. I have not started any ipkg zone or any vm and now the host is running stable. Thanks in advance. -- Groeten, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] crash after upgrading to 151024
hi, Not even two days ago I posted my message with a crash after updating to the latest omniosce. I am happy to report that the issue has been fixed by Andy Fiddaman (yesterday I updated to r151024) and everything is working: all the ipkg and lx zones plus de vm's hosted in the nfs serve Thanks for the very fast fix to a humble home user. Amazing response. -- regards, Natxo On Sun, Nov 19, 2017 at 10:22 PM, Andy Fiddaman <omn...@citrus-it.net> wrote: > > On Sun, 19 Nov 2017, Natxo Asenjo wrote: > > ; hi, > ; > ; I upgraded our home nas from the old stable ce to the new stable one. The > ; process went ok, but after rebooting it has crashed twice: > ; > ; panicstack = unix:die+df () | unix:trap+e08 () | > ; unix:_cmntrap+e6 () | unix:strncpy+28 () | lx_brand:lx_prctl+48a () | > ; lx_brand:lx_syscall_enter+16f () | unix:brand_sys_syscall+1bd () | > > This looks like a bug in the lx support in r151024 with a commit that came > in fairly recently (so wouldn't have been in r151022). Send me the crash > dump as per the private email I've sent you but I think I can see where > this is (and the problem) just from the above. The crash dump will confirm > and then we'll get it fixed in the next r151024 update. > > Andy > > -- > Citrus IT Limited | +44 (0)333 0124 007 | enquir...@citrus-it.co.uk > Rock House Farm | Green Moor | Wortley | Sheffield | S35 7DQ > Registered in England and Wales | Company number 4899123 > > -- -- Groeten, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] [ot] recommendation on jbod enclosure (16-bay, preferably 24 bay) 2.5 inch sas/sata
hi, the subject says it all, I guess. I am based in The Netherlands, but buying in the EU should be ok. I can only find very expensive Dell or HP kit (> EUR 5000) but I cannot seem to find in here something like this: https://www.neweggbusiness.com/product/product.aspx?item=9b-1uw-0036-00096 which looks a lot like what we are after Thanks in advance! -- Regards, Natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] omnios not updating
ok, rebooting solved this non issue. Sorry for the noise On Fri, Jan 5, 2018 at 8:26 PM, Natxo Asenjo <natxo.ase...@gmail.com> wrote: > hi, > > my home filer running OmniOS v11 r151024d keeps updating the same set of > packages: > > # pkg update -v > WARNING: The boot environment being modified is not the active one. > Changes > made in the active BE will not be reflected on the next boot. > > Packages to update: 7 > Estimated space available: 198.39 GB > Estimated space to be consumed: 116.78 MB >Create boot environment: Yes > Activate boot environment: Yes > Create backup boot environment:No > Rebuild boot archive: Yes > > Changed packages: > omnios > editor/vim > 8.0.586-0.151024:20171030T140745Z -> 8.0.586-0.151024:20171201T220955Z > library/nspr > 4.17-0.151024:20171030T152143Z -> 4.17-0.151024:20171213T000253Z > library/security/openssl > 1.0.2.13-0.151024 -> 1.0.2.14-0.151024 > network/rsync > 3.1.2-0.151024:20171030T152409Z -> 3.1.2-0.151024:20171207T202651Z > release/name > 0.5.11-0.151024:20171129T095705Z -> 0.5.11-0.151024:20171218T121347Z > system/kernel/dtrace/providers > 0.5.11-0.151024:20171030T151622Z -> 0.5.11-0.151024:20171203T191145Z > system/library/mozilla-nss > 3.33-0.151024:20171030T152105Z -> 3.33-0.151024:20171213T000211Z > > It runs correctly, I get this message: > > A clone of r151024-1 exists and has been updated and activated. > On the next boot the Boot Environment r151024-6 will be > mounted on '/'. Reboot when ready to switch to this updated BE. > > Updating package cache 1/1 > > > --- > NOTE: Please review release notes posted at: > > http://www.omniosce.org/releasenotes > > But after rebooting If I retry pkg update -nv, I see the same set of > available patches. If I run pkg history, the last patched date is last > month: > > 2017-12-10T14:04:54 refresh-publishers pkg > Succeeded > 2017-12-10T14:04:55 rebuild-image-catalogs pkg > Succeeded > 2017-12-19T20:31:07 refresh-publishers pkg > Succeeded > 2017-12-19T20:31:09 rebuild-image-catalogs pkg > Succeeded > > > Any idea as to what is going on? ;-) > > Thanks! > -- > Groeten, > natxo > -- -- Groeten, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] omnios not updating
hi, my home filer running OmniOS v11 r151024d keeps updating the same set of packages: # pkg update -v WARNING: The boot environment being modified is not the active one. Changes made in the active BE will not be reflected on the next boot. Packages to update: 7 Estimated space available: 198.39 GB Estimated space to be consumed: 116.78 MB Create boot environment: Yes Activate boot environment: Yes Create backup boot environment:No Rebuild boot archive: Yes Changed packages: omnios editor/vim 8.0.586-0.151024:20171030T140745Z -> 8.0.586-0.151024:20171201T220955Z library/nspr 4.17-0.151024:20171030T152143Z -> 4.17-0.151024:20171213T000253Z library/security/openssl 1.0.2.13-0.151024 -> 1.0.2.14-0.151024 network/rsync 3.1.2-0.151024:20171030T152409Z -> 3.1.2-0.151024:20171207T202651Z release/name 0.5.11-0.151024:20171129T095705Z -> 0.5.11-0.151024:20171218T121347Z system/kernel/dtrace/providers 0.5.11-0.151024:20171030T151622Z -> 0.5.11-0.151024:20171203T191145Z system/library/mozilla-nss 3.33-0.151024:20171030T152105Z -> 3.33-0.151024:20171213T000211Z It runs correctly, I get this message: A clone of r151024-1 exists and has been updated and activated. On the next boot the Boot Environment r151024-6 will be mounted on '/'. Reboot when ready to switch to this updated BE. Updating package cache 1/1 --- NOTE: Please review release notes posted at: http://www.omniosce.org/releasenotes But after rebooting If I retry pkg update -nv, I see the same set of available patches. If I run pkg history, the last patched date is last month: 2017-12-10T14:04:54 refresh-publishers pkg Succeeded 2017-12-10T14:04:55 rebuild-image-catalogs pkg Succeeded 2017-12-19T20:31:07 refresh-publishers pkg Succeeded 2017-12-19T20:31:09 rebuild-image-catalogs pkg Succeeded Any idea as to what is going on? ;-) Thanks! -- Groeten, natxo ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss