Re: [OpenIndiana-discuss] ZVOL (et al) /device node access rights
Hello, I have impression that it is not always necessary to chown raw zvol's. It happens occasionally on some zvols (and only when I initiate reboot and forget about it) :) Regards Andrej On Sun, Oct 14, 2012 at 3:08 PM, Jim Klimov j...@cos.ru wrote: While updating the Wiki page on virtualization, Edward Ned Harvey wrote of, and brought to my attention, this peculiar situation: A VirtualBox VM can use delegated zvols as dsk or rdsk devices on the host, just like it can use delegated raw disks or partitions, likely iSCSI volumes and other block devices. According to Edward, block devices yield better performance than VDI files for VM disks. A VM can be executed by an unprivileged user, and thus the device node needs to be RW accessible to that non-root user (whom and why to trust - that's the admin's problem, OS should not limit that). So, the problem detected with ZVOLs (and I expect it can have a wider range on other devices) is that the ownership of the device node for a zvol is forgotten upon reboot or other pool reimport. That is, the node used by a VM should be chown'ed upon every VM startup. That's inconvenient, so to say. I played more with this and found that I can also set ACLs with /bin/chmod on device nodes, and that is even remembered across reboots, however with /dev/zvol/*dsk/pool/vol being a dynamically assigned symlink like /devices/pseudo/zfs@0:4(,raw) there is a problem: the symlink and device node is created when I look at it (i.e. upon first ls or another access to the /dev/zvol/... object), and the device node occupies the first available number. The /devices filesystem seems to remember ACL entries (but not ownerships) across reboots only in conjunction with its object names, so upon each reboot (reimport) of the pool, the same device node name can get assigned to different zvols. This is not only useless in terms of stably providing access to certain devices for certain users, but also harmful as after a reboot an unexpected user (among those earlier trusted) can gain access to incorrect devices (and might even enforce that somehow, by being first to access the device at the correct moment) and cause DoS or intentional illicit access to other users' data. So here is the picture as is. I am not sure what exactly to ask, so I guess it's a call for opinions on how the situation can be improved, in terms of remembering correct ownerships and ACLs for those devices (not nodes) that the rights were set for, in order to both increase usability and security of non-root device access. In the particular case of ZVOL devices, I guess attributes can be added to the ZVOLs that would hold the POSIX and ACL access rights and owner:group info (do people agree that is a worthy RFE?). For non-zfs devices like local disk or iscsi or USB - I am not sure if the problem exists the same way (not tested) or how it can be addressed if it exists (some config file for devfs?) Thanks, //Jim Klimov __**_ OpenIndiana-discuss mailing list OpenIndiana-discuss@**openindiana.orgOpenIndiana-discuss@openindiana.org http://openindiana.org/**mailman/listinfo/openindiana-**discusshttp://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] KVM and Xen support in OpenIndiana
Hello all, at the moment I am search for alternativ OSes than linux which have KVM and Xen support. beside NetBSD and Illumos I also want to look at OpenIndiana. For KVM I found a port at github which semm to work but is in a testing/development state. For Xen I couldn't find that much so for me it's not clear if there is Dom0 support in OpenIndiana or whether there are plans to implement Dom0 support. When someone know more about that themes it would be great to get a reply with more information. Best Regards ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] KVM and Xen support in OpenIndiana
Lukas Laukamp wrote: Hello all, at the moment I am search for alternativ OSes than linux which have KVM and Xen support. beside NetBSD and Illumos I also want to look at OpenIndiana. For KVM I found a port at github which semm to work but is in a testing/development state. For Xen I couldn't find that much so for me it's not clear if there is Dom0 support in OpenIndiana or whether there are plans to implement Dom0 support. When someone know more about that themes it would be great to get a reply with more information. Hi to All new to Solaris and Illumos based, Openiniana :) I hope you will find many benefits in using Solaris / Illumos based systems but you _really get to know what you will get with it's benefits_ and where it shines comparing to other platforms. If you know it, I hope choosing it would be more easy, primary from Sysadmin perspective that wants to have a life more easy and safer in a sense of doing your work like you expect. List of Illumos distributions: http://wiki.illumos.org/display/illumos/Distributions Those benefits include open source engineered Kernel with ZFS on the upstream, Light virtualization with Zones, network virtualization with crossbow, KVM integration, DTrace for live server debugging, better hardware scalability, binary compatibility of applications between releases, stable driver ABI, boot environments/snapshots,IP2 mutipathing/Load balancing, role based access control, etc. Openindiana is Illumos based distribution, with IPS packaging as continuation of Opensolaris and is made of mostly same user space packages as Solaris11, plus OI additional IPS publishers/repositories. It is available both in text-only install (server) and with Desktop, as the truly Opensolaris continuation. http://wiki.openindiana.org/oi/1.+Introduction https://hg.openindiana.org/ http://wiki.openindiana.org/oi/Package+Repositories KVM for Illumos is made for SmartOS (Joyent company made it for a cloud) and is now available in Openindiana. Officially, KVM for Illumos supports Intel CPU's with EPT instruction set. http://wiki.openindiana.org/oi/KVM Illumos KVM is used in production in Joyent for large scale virtualization for real-world customers and is available in Openindiana. Version for AMD CPUs and Intel without EPT is in development and need community backing. http://wiki.smartos.org/display/DOC/Hardware+Requirements#HardwareRequirements-KVMRequirements https://github.com/jclulow/illumos-kvm/ Illumos distributions and Openindiana support running as domU . Xen (dom0) support was available in Opensolaris 2009.06 till Opensolaris snv_134 , but aether Oracle ditched it from source before renamed it to it's closed source product on Solaris11, and Illumos does not have it in the code tree, because it was removed from OS/Net before Oracle forked it to closed source and Illumos established itself. So kernel implementation and source for Xen dom0 exists, but needs to be revived and renewsed for Illumos ,included back and developed further, just community need to activate itself with _supporting development where it is left. Same goes for Open HA - high availability that was last time available for Opensolaris 2009.06 (111b) and was tighten to release binaries. It would also be nice to have community backing it and reviving it or at least preparing it for OI stable to be released with it. But there is working alternative, based on **PaceMaker/ Heartbeat , see: http://wiki.openindiana.org/pages/viewpage.action?pageId=23855106 Hope this is all you need for a start :) ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] KVM and Xen support in OpenIndiana
Am 15.10.2012 10:44, schrieb Nikola M: Lukas Laukamp wrote: Hello all, at the moment I am search for alternativ OSes than linux which have KVM and Xen support. beside NetBSD and Illumos I also want to look at OpenIndiana. For KVM I found a port at github which semm to work but is in a testing/development state. For Xen I couldn't find that much so for me it's not clear if there is Dom0 support in OpenIndiana or whether there are plans to implement Dom0 support. When someone know more about that themes it would be great to get a reply with more information. Hi to All new to Solaris and Illumos based, Openiniana :) I hope you will find many benefits in using Solaris / Illumos based systems but you _really get to know what you will get with it's benefits_ and where it shines comparing to other platforms. If you know it, I hope choosing it would be more easy, primary from Sysadmin perspective that wants to have a life more easy and safer in a sense of doing your work like you expect. List of Illumos distributions: http://wiki.illumos.org/display/illumos/Distributions Those benefits include open source engineered Kernel with ZFS on the upstream, Light virtualization with Zones, network virtualization with crossbow, KVM integration, DTrace for live server debugging, better hardware scalability, binary compatibility of applications between releases, stable driver ABI, boot environments/snapshots,IP2 mutipathing/Load balancing, role based access control, etc. Openindiana is Illumos based distribution, with IPS packaging as continuation of Opensolaris and is made of mostly same user space packages as Solaris11, plus OI additional IPS publishers/repositories. It is available both in text-only install (server) and with Desktop, as the truly Opensolaris continuation. http://wiki.openindiana.org/oi/1.+Introduction https://hg.openindiana.org/ http://wiki.openindiana.org/oi/Package+Repositories KVM for Illumos is made for SmartOS (Joyent company made it for a cloud) and is now available in Openindiana. Officially, KVM for Illumos supports Intel CPU's with EPT instruction set. http://wiki.openindiana.org/oi/KVM Illumos KVM is used in production in Joyent for large scale virtualization for real-world customers and is available in Openindiana. Version for AMD CPUs and Intel without EPT is in development and need community backing. http://wiki.smartos.org/display/DOC/Hardware+Requirements#HardwareRequirements-KVMRequirements https://github.com/jclulow/illumos-kvm/ Illumos distributions and Openindiana support running as domU . Xen (dom0) support was available in Opensolaris 2009.06 till Opensolaris snv_134 , but aether Oracle ditched it from source before renamed it to it's closed source product on Solaris11, and Illumos does not have it in the code tree, because it was removed from OS/Net before Oracle forked it to closed source and Illumos established itself. So kernel implementation and source for Xen dom0 exists, but needs to be revived and renewsed for Illumos ,included back and developed further, just community need to activate itself with _supporting development where it is left. Same goes for Open HA - high availability that was last time available for Opensolaris 2009.06 (111b) and was tighten to release binaries. It would also be nice to have community backing it and reviving it or at least preparing it for OI stable to be released with it. But there is working alternative, based on **PaceMaker/ Heartbeat , see: http://wiki.openindiana.org/pages/viewpage.action?pageId=23855106 Hope this is all you need for a start :) Hello Nicola, thanks for that comprehensiv reply. Unfortonatly I am not that good in software development to do such a thing. I could only help the development with testing results and so on. I think there must be found a few people who are interested in Xen Support for Illumos/OpenIndiana. So I don't know what I could do to get more involved in such a process. Eventually someone has an idea how I can get more involved in such a development process. Best Regards ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] KVM and Xen support in OpenIndiana
Lukas Laukamp wrote: thing. I could only help the development with testing results and so on. I think there must be found a few people who are interested in Xen Support for Illumos/OpenIndiana. So I don't know what I could do It is important to know that Xen is there but needs maintance. But there must be some reasons Joyent ported KVM instead, so there is KVM working we can use in OI and also there is working Virtualbox for Solaris made by Oracle programmers, that works on Openindiana. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] KVM and Xen support in OpenIndiana
We have Linux and Windows 2008 R2 servers running at different sites in KVM machines and it works a treat (if you have all the passthrough stuff on Intel chips turned on) IIRC Joyent went for KVM because the speed was better, support from the community was better and because the XEN stuff that already existed kinda needed to be chucked out and re-written. I get the feeling that this might be a VHS vs. BetaMax for us, but as I said KVM works a charm for me. Jon On 15 October 2012 11:02, Nikola M minik...@gmail.com wrote: Lukas Laukamp wrote: But there must be some reasons Joyent ported KVM instead, so there is KVM working we can use in OI and also there is working Virtualbox for Solaris made by Oracle programmers, that works on Openindiana. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] KVM and Xen support in OpenIndiana
Lukas Laukamp wrote: Am 15.10.2012 11:42, schrieb Nikola M: Lukas Laukamp wrote: thing. I could only help the development with testing results and so on. I think there must be found a few people who are interested in Xen Support for Illumos/OpenIndiana. So I don't know what I could do It is important to know that Xen is there but needs maintance. But there must be some reasons Joyent ported KVM instead, so there is KVM working we can use in OI and also there is working Virtualbox for Solaris made by Oracle programmers, that works on Openindiana. So the way would be to merge the Dom0 support from the Solaris Repos, try to compile it and fix eventual problems? Best Regards No, Xen Dom0 is part of OS/Net consolidation, that is Actually SunOS (Kernel+base system). Oracle ditched Xen support/code from Opensolaris OS/Net , prior starting to build it's closed source fork for Solaris11 Express and later Solaris11 (And It probably ended up in it's closed source Oracle VM). Illumos did not had it aether, since it also contiued to build upon latest OS/Net available at a time and is named Illumos after replacing many closed parts with open ones. So code for Xen dom0 is available in Opensolaris in versions of OS/Net prior both Illumos and S11Express. It needs XEN kernel engineer who understand Solaris kernel internals and Illumos, to pick it up and develop it for Illumos .. and I suppose funding for it from interested parties. But KVM is working for Illumos now , thanks to Joyent developers, so you can use it. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] KVM and Xen support in OpenIndiana
On Mon, 15 Oct 2012, Jonathan Adams wrote: We have Linux and Windows 2008 R2 servers running at different sites in KVM machines and it works a treat (if you have all the passthrough stuff on Intel chips turned on) Is OpenIndiana's KVM usable for running a desktop OS like Windows 7 with use of the Windows GUI console (keyboard, mouse, video)? From a desktop usability standpoint, how would it compare with VirtualBox? From my experience VirtualBox provides and excellent guest desktop experience (even works great for Netflix video streaming with Windows 7 guest) but that CPU and filesystem performance may suffer. I have shrink-wrapped Windows 7 waiting to be installed here and I must decide between KVM and VirtualBox. I understand that KVM and VirtualBox can not run simultaneously due to their use of the CPU. It might be possible to share a common image and switch between the two, but the available devices might change and that would cause issues for Windows. Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ZVOL (et al) /device node access rights
Hello, I'm running VB guests as normal (unprivileged) user and I have impression that ownership (I'm using chown on zvol's) is not always lost during reboot. The other part of my comment was joke on my behalf, since restarts of host OS are rare and often I forget to check if guests came up properly. But I completely agree with you that the behaviour is not favorable. Regards Andrej On Mon, Oct 15, 2012 at 4:39 PM, Jim Klimov jimkli...@cos.ru wrote: I am not sure I understood your comment?.. 2012-10-15 11:14, Andrej Javoršek wrote: Hello, I have impression that it is not always necessary to chown raw zvol's. It seems necessary when we need to allow a non-root user to use the zvol directly, such as a backing store for his VM's virtual disk. It happens occasionally on some zvols (and only when I initiate reboot and forget about it) :) What happens? The need to chown? Sorry for misunderstandings if any, //Jim Regards Andrej On Sun, Oct 14, 2012 at 3:08 PM, Jim Klimov j...@cos.ru wrote: While updating the Wiki page on virtualization, Edward Ned Harvey wrote of, and brought to my attention, this peculiar situation: A VirtualBox VM can use delegated zvols as dsk or rdsk devices on the host, just like it can use delegated raw disks or partitions, likely iSCSI volumes and other block devices. According to Edward, block devices yield better performance than VDI files for VM disks. A VM can be executed by an unprivileged user, and thus the device node needs to be RW accessible to that non-root user (whom and why to trust - that's the admin's problem, OS should not limit that). So, the problem detected with ZVOLs (and I expect it can have a wider range on other devices) is that the ownership of the device node for a zvol is forgotten upon reboot or other pool reimport. That is, the node used by a VM should be chown'ed upon every VM startup. That's inconvenient, so to say. I played more with this and found that I can also set ACLs with /bin/chmod on device nodes, and that is even remembered across reboots, however with /dev/zvol/*dsk/pool/vol being a dynamically assigned symlink like /devices/pseudo/zfs@0:4(,raw) there is a problem: the symlink and device node is created when I look at it (i.e. upon first ls or another access to the /dev/zvol/... object), and the device node occupies the first available number. The /devices filesystem seems to remember ACL entries (but not ownerships) across reboots only in conjunction with its object names, so upon each reboot (reimport) of the pool, the same device node name can get assigned to different zvols. This is not only useless in terms of stably providing access to certain devices for certain users, but also harmful as after a reboot an unexpected user (among those earlier trusted) can gain access to incorrect devices (and might even enforce that somehow, by being first to access the device at the correct moment) and cause DoS or intentional illicit access to other users' data. So here is the picture as is. I am not sure what exactly to ask, so I guess it's a call for opinions on how the situation can be improved, in terms of remembering correct ownerships and ACLs for those devices (not nodes) that the rights were set for, in order to both increase usability and security of non-root device access. In the particular case of ZVOL devices, I guess attributes can be added to the ZVOLs that would hold the POSIX and ACL access rights and owner:group info (do people agree that is a worthy RFE?). For non-zfs devices like local disk or iscsi or USB - I am not sure if the problem exists the same way (not tested) or how it can be addressed if it exists (some config file for devfs?) Thanks, //Jim Klimov ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] I am having problems with Inkscape and convert producing PNG's
On Mon, 15 Oct 2012, Jonathan Adams wrote: it's the same message on both, I'm not sure if Inkscape is using convert to produce the file. jadams@jadlaptop:~/images$ convert Mylogo.svg /tmp/Mylogo.png convert: Application was compiled with png.h from libpng-1.2.44 `/tmp/Mylogo.png' @ warning/png.c/MagickPNGWarningHandler/1781. convert: Application is running with png.c from libpng-1.4.3 `/tmp/Mylogo.png' @ warning/png.c/MagickPNGWarningHandler/1781. convert: Incompatible libpng version in application and library `/tmp/Mylogo.png' @ warning/png.c/MagickPNGWarningHandler/1781. convert: memory allocation failed `/tmp/Mylogo.png' @ error/png.c/WriteOnePNGImage/8873. jadams@jadlaptop:/sal/images$ pkg list | egrep -i inkscape|png|magick image/editor/imagemagick (sfe)6.7.6.10-0.151.1.5 i-- image/editor/inkscape (sfe) 0.48.2-0.151.1.5 i-- image/library/g++/imagemagick (sfe) 6.7.6.10-0.151.1.5 i-- image/library/libpng 0.5.11-0.151.1.7 i-- SFE ImageMagick has a bug and this should be reported to the OpenIndiana SFE bug tracker. The bug can be illustrated by executing 'convert -list format' and looking at the details for PNG: PNG* PNG rw- Portable Network Graphics (libpng 1.2.44,1.4.3) See http://www.libpng.org/ for details about the PNG format. What the error messages and the PNG detail information is telling us is that the png headers used do not match the png library used. Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Memory usage concern
Thanks for the responses. Spot on in post http://openindiana.org/**pipermail/openindiana-discuss/** 2012-September/009788.htmlhttp://openindiana.org/pipermail/openindiana-discuss/2012-September/009788.html arc_meta_used = 423 MB 2 days later arc_meta_used = 827 MB thanks, On Fri, Oct 12, 2012 at 12:32 PM, Roel_D openindi...@out-side.nl wrote: Hmz, i'm running multiple windows 2003 servers within virtualbox running on Solaris 10 hosts. Some windows servers are online for almost a year now. The VHD's are stored on a Zfs mirror and i never had any out-of-memory errors. The solaris servers also serve glassfish, mysqlcluster and many, many more services from zones. Running out of memory can imho only be caused by a programmingerror in the virtualbox version. Zfs will not cause an out-of-memory Kind regards, The out-side Op 12 okt. 2012 om 18:13 heeft Udo Grabowski (IMK) udo.grabow...@kit.edu het volgende geschreven: On 12/10/2012 16:10, Heinrich van Riel wrote: My concern is as follow, when I 1st start the system and VMs there is 8GB of free memory. This number keeps decreasing by about 300MB every 10 hours. OI - 10GB max allocated to ZFS ARC (only setting change from default install) At the current rate there will be no memory free in 10 days. Am I concerned for no reason? This can impact your other work to do on that machine severely. However, if that is only a fileserver, ZFS will manage to keep some memory available so that the machine will not swap if nothing else interferes. Insofar Damians comments on unused RAM are correct. But if you know you need space for something else often, see my remedies for this problem in this thread: http://openindiana.org/pipermail/openindiana-discuss/2012-September/009788.html -- Dr.Udo GrabowskiInst.f.Meteorology a.Climate Research IMK-ASF-SAT www-imk.fzk.de/asf/sat/grabowski/ www.imk-asf.kit.edu/english/sat.php KIT - Karlsruhe Institute of Technologyhttp://www.kit.edu Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026 ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] I am having problems with Inkscape and convert producing PNG's
On 10/15/12 05:05 PM, Jonathan Adams wrote: it's the same message on both, I'm not sure if Inkscape is using convert to produce the file. jadams@jadlaptop:~/images$ convert Mylogo.svg /tmp/Mylogo.png convert: Application was compiled with png.h from libpng-1.2.44 `/tmp/Mylogo.png' @ warning/png.c/MagickPNGWarningHandler/1781. convert: Application is running with png.c from libpng-1.4.3 `/tmp/Mylogo.png' @ warning/png.c/MagickPNGWarningHandler/1781. convert: Incompatible libpng version in application and library `/tmp/Mylogo.png' @ warning/png.c/MagickPNGWarningHandler/1781. convert: memory allocation failed `/tmp/Mylogo.png' @ error/png.c/WriteOnePNGImage/8873. jadams@jadlaptop:/sal/images$ pkg list | egrep -i inkscape|png|magick image/editor/imagemagick (sfe)6.7.6.10-0.151.1.5 i-- image/editor/inkscape (sfe) 0.48.2-0.151.1.5 i-- image/library/g++/imagemagick (sfe) 6.7.6.10-0.151.1.5 i-- image/library/libpng 0.5.11-0.151.1.7 i-- Any suggestions on what to install to get this working? :) This is a annoying problem with nearly everything that's linked to png or cairo. I usually run with env LD_PRELOAD=/usr/lib/libpng12.so convert but I don't know if libpng12 was intended (I suspect not), and if not, if the called functions really do the same as the libpng14 ones (save the ones not in libpng12). At least the images produced look ok. This was a build error present also on some Linux systems, and should be cleaned up, since a lot of programs and libraries using or linking to libpng-dependent stuff are affected and break without some workaround. I don't know if it is possible to build some wrapper libpng as a workaround which can solve this until this mess fixed, but I don't have any clue how to trick out the version check in such a library. Maybe someone else has an idea. -- Dr.Udo GrabowskiInst.f.Meteorology a.Climate Research IMK-ASF-SAT www-imk.fzk.de/asf/sat/grabowski/ www.imk-asf.kit.edu/english/sat.php KIT - Karlsruhe Institute of Technologyhttp://www.kit.edu Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026 ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] I am having problems with Inkscape and convert producing PNG's
On Mon, 15 Oct 2012, Udo Grabowski (IMK) wrote: Any suggestions on what to install to get this working? :) This is a annoying problem with nearly everything that's linked to png or cairo. I usually run with env LD_PRELOAD=/usr/lib/libpng12.so convert but I don't know if libpng12 was intended (I suspect not), and if not, if the called functions really do the same as the libpng14 ones (save the ones not in libpng12). At least the images produced look ok. The libpng 1.4 structures are not identical to 1.2. If it seems to be working it is due to pleasant accident. This was a build error present also on some Linux systems, and should be cleaned up, since a lot of programs and libraries using or linking to libpng-dependent stuff are affected and break without some workaround. I don't know if it is possible to build some wrapper libpng as a workaround which can solve this until this mess fixed, but I don't have any clue how to trick out the version check in such a library. Maybe someone else has an idea. The problem is that library dependencies are causing two versions of libpng to be pulled into the same program: % ldd `which convert`|grep png libpng14.so.14 =/usr/lib/libpng14.so.14 libpng12.so.0 = /usr/lib/libpng12.so.0 Unless ELF symbol versioning is used in the library, then lazy symbol loading might cause functions from either library to be used, depending on the sequence of events. Unless the code using libpng12 can be updated to use libpng14 then the simplest solution is to re-build ImageMagick so that it uses libpng 1.2. Libpng 1.5 has improved its interface so that the applications can no longer access libpng structure members directly. This is a huge improvement but requires that all of the using code be updated to use the new API. Libpng 1.4 offers the new API in a transitional mode to allow applications time to update. Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Memory usage concern
It seems the memory is going to the kernel. I have this problem on my web proxy tier, but not on my backend systems. I have checked kernel core dumps for memory leaks, switched the Ethernet cards/drivers, tested exclusive versus shared interfaces on the zones, and tweaked everything I could think of. I haven't found a solution. I run the same motherboard every where and I only have this issue on the proxy tier. I put 96gb of ram in one box and watched the system consume it all. Ultimately, I increased the RAM across the board to push the reboot cycle out a couple of weeks. My longer term plan is to develop the software stack on Linux and migrate the proxy tier to CentOS. It sickens me that we can't get this right, but if Linux is the best tool for the job then that's what I will use. Fortunately, the data tier doesn't suffer from this problem and that's where we really need the data handling capabilities of ZFS. My hardware platform on the web tier is Intel SR2625URLX, LSI 9211-8i, Crucial M4s for storage. The primary application running is nginx. I have nearly no writes to disk. We have such a fire hose of http traffic that we cannot possibly write logs on the proxy tier. By the way, it is nice to find you. James Carlson insisted I was the only one having this problem ;-) j. root@www003:~# for i in `seq 1 5`; do date; echo ::memstat |mdb -k |egrep Kernel|MB; sleep 120; done October 15, 2012 03:32:37 PM PDT Page SummaryPagesMB %Tot Kernel3659602 14295 44% October 15, 2012 03:34:39 PM PDT Page SummaryPagesMB %Tot Kernel3660353 14298 44% October 15, 2012 03:36:41 PM PDT Page SummaryPagesMB %Tot Kernel3661008 14300 44% October 15, 2012 03:38:43 PM PDT Page SummaryPagesMB %Tot Kernel3661708 14303 44% October 15, 2012 03:40:45 PM PDT Page SummaryPagesMB %Tot Kernel3662362 14306 44% ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Memory usage concern
I can't tell you much about continuus use of VirtualBox and its stability over long periods of time, I used it with success on daily basis for few years now, with OI (and previously OpenSolaris) being host. I've seen no problems with stability, however I only run it for a day and then whole system was powered down for night. I have this problem without virtual box. The system consumes memory until it gets down to a couple of hundred megabytes. By then, network response times shoot up. Since I collect this data, I can also tell you that there are periodic resets where the response time improves for some period of time. The cycle continues until the system crashes due to memory starvation. j. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Memory usage concern
On 16 October 2012 00:52, Jason Matthews ja...@broken.net wrote: I should also mention that over all network performance degrades over time and the only fix I have sound so far is to shut down the zones, destroy the vnics, recreate them, and then reboot the zones. I do that about every four hours to keep the response times reasonable. It really sucks. IMO you blame the wrong people. You can have the same kind of problems with any Illumos-based distribution if you activate a zone and let the machine just sit there for a week or so or have a lot filesystem activity using mmap(). Either way the machines will choke themselves to memory starvation. The only workaround we found are regular reboots (every 24h), or limit the ZFS ARC to an absolute minimum. Ced -- Cedric Blancher cedric.blanc...@googlemail.com Institute Pasteur ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Memory usage concern
-Original Message- From: Cedric Blancher [mailto:cedric.blanc...@googlemail.com] IMO you blame the wrong people. You can have the same kind of problems with any Illumos-based distribution if you activate a zone and let the machine just sit there for a week or so or have a lot filesystem activity using mmap(). Either way the machines will choke themselves to memory starvation. The only workaround we found are regular reboots (every 24h), or limit the ZFS ARC to an absolute minimum. I don't think you understand. My proxy tier does almost no reads from the file system. There is no content on the server. The ARC is irrelevant. ZFS isn't consuming the memory and if it did, it would give it up, given enough memory pressure. The proxy tier is simply a proxy to another system in the back end which also runs nginx. The backend systems, run nginx, Postgres, and some other utility scripts to push bits where they need to go. The backend systems do, as reported by zpool iostat, about 10k writes/second (up to about 50MB/s). There are way more back end systems than proxy tier systems and the backend runs just fine. Most will achieve a year of uptime in November. I have two radically different behaviors, on the same hardware platform, running essentially the same software stack where the major difference is the fire hose of network activity. In addition, to say that a zone needs to be rebooted every twenty-four hours is nuts. If this is what you are doing, then I fully do not understand your position. j. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Zfs stability Scrubs
On Mon, Oct 15, 2012 at 6:21 PM, Jason Matthews ja...@broken.net wrote: From: heinrich.vanr...@gmail.com [mailto:heinrich.vanr...@gmail.com] My point is most high end storage units has some form of data verification process that is active all the time. As does ZFS. The blocks are checksumed on each read. Assuming you have mirrors or parity redundancy, the misbehaving block is corrected, reallocated, etc. Right, I understand ZFS checks data on each read, my point is checking the disk or data periodically. In my opinion scrubs should be considered depending on the importance of data and the frequency based on what type of raidz, change rates and disk type used. One point of scrubs is to verify the data that you don't normally read. Otherwise, the errors would be found in real time upon the next read. Understood, if full backups are executed weekly/monthly no scrub is required. Perhaps in future ZFS will have the ability to limit resource allocation when scrubbing like with BV where it can be set. Rebuild priory can also be set. There are tunables for this. Thanks, did not know will research, had a fairly heavy impact the other day replacing a disk.. Also some high end controllers have port verify for each disk (media read) when using their integrated raid that runs periodically. Since in the world of ZFS it is recommended to use JBOD I see it as more than just the filesystem. I have never deployed a system containing mission critical data using filesystem raid protection other than with ZFS since there is no protection in them an I would much rather bank on the controller. Unfortunately my parser was unable to grok this. Seems like you would prefer a raid controller. Sorry, boils down to this, if ZFS is not an option I use a raid controller if data is important. In fact I do not like to be tied to a specific controller, zfs gives me the freedom to change at any point j. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Zfs stability Scrubs
On Oct 15, 2012, at 3:00 PM, heinrich.vanr...@gmail.com wrote: Most of my storage background is with EMC CX and VNX and that is used in a vast amount of datacenters. They run a process called sniiffer that runs in the background and request a read of all blocks on each disk individually for a specific LUN, if there is an unrecoverable read error a Background Verify (BV) is requested by the process to check for data consistency. The unit will also conduct a proactive copy to a hotspare, I believe once data has been verified, from the disk where the error(s) were seen. A BV is also requested when there is a LUN failover, enclosure path failure or a storage processor failure. My point is most high end storage units has some form of data verification process that is active all the time. Don't assume BV is data verification. On most midrange- systems these scrubbers just check for disks to report errors. While this should catch most media errors, it does not catch phantom writes or other corruption in the datapath. On systems with SATA disks, there is no way to add any additional checksums to the sector, so they are SOL if there is data corruption that does not also cause a disk failure. For SAS or FC disks, some vendors use larger sectors and include per-sector checksums that can help catch some phantom write or datapath corruption. There is some interesting research that shows how scrubs for RAID-5 systems can contaminate otherwise good data. The reason is that if a RAID-5 parity mismatch occurs, how do you know where the data corruption is when the disks themselves do not fail. In those cases, scrubs are evil. ZFS does not suffer from this problem because the checksums are stored in the parent's metadata. In my opinion scrubs should be considered depending on the importance of data and the frequency based on what type of raidz, change rates and disk type used. Perhaps in future ZFS will have the ability to limit resource allocation when scrubbing like with BV where it can be set. Rebuild priory can also be set. Throttling exists today, but most people don't consider mdb as a suitable method for setting :-( Scrub priority is already lowest priority, I don't see much need to increase it. -- richard Also some high end controllers have port verify for each disk (media read) when using their integrated raid that runs periodically. Since in the world of ZFS it is recommended to use JBOD I see it as more than just the filesystem. I have never deployed a system containing mission critical data using filesystem raid protection other than with ZFS since there is no protection in them an I would much rather bank on the controller. my few cents on scrubs. Thanks From: Jim Klimov Sent: October 13, 2012 9:02 To: Discussion list for OpenIndiana Subject: Re: [OpenIndiana-discuss] Zfs stability Scrubs 2012-10-13 7:26, Michael Stapleton wrote: The VAST majority of data centers are not storing data in storage that does checksums to verify data, that is just the reality. Regular backups and site replication rule. And this actually concerns me... we help maintain some deployments built by customers including professional arrays like Sun Storagetek 6140 serving a few LUNs to directly attached servers (so it happens). The arrays are black boxes to us - we don't know if they use something block-checksummed similar to ZFS inside, or can only protect against whole-disk failures, when a device just stops responding? We still have little idea - in what config would the data be safer to hold a ZFS pool, and which should give more performance: * if we use the array with its internal RAID6, and the client computer makes a pool over the single LUN * a couple of RAID6 array boxes in a mirror provided by arrays' firmware (independently of client computers, who see a MPxIO target LUN), and the computer makes a pool over the single multi-pathed LUN * a couple of RAID6 array boxes in a mirror provided by ZFS (two independent LUNs mirrored by computer) * serve LUNs from each disk in JBOD manner from the one or two arrays, and have ZFS construct pools over that. Having expensive hardware RAIDs (anyway available on customer's site) serving as JBODs is kind of overkill - any well-built JBOD costing a fraction of this array could suffice. But regarding data integrity known to be provided by ZFS and unknown to be really provided by black-box appliances, downgrading the arrays to JBODs might be better. Who knows?.. (We don't, advice welcome). There are several more things to think about: 1) Redundant configs without knowledge of which side of the mirror is good, or what permutation of RAID blocks yields the correct answer, is basically useless, and it can propagate errors by overwriting an unknownly-good copy of the data with unknownly- corrupted one. For
Re: [OpenIndiana-discuss] Zfs stability Scrubs
2012-10-16 3:57, Heinrich van Riel wrote: Understood, if full backups are executed weekly/monthly no scrub is required. I'd argue that this is not a completely true statement. It might hold for raidzN backing storage with single-copy blocks, but if mirrors and/or two or three copies are involved (i.e. for metadata blocks) or ditto blocks on deduped pools, you have say a 50/50 or 33/67 chance of only reading once a particular copy of a block during the backup'ing procedure, and if errors hide in other copies - you'll miss them. That's where scrub should shine, by enforcing reads of all copies of all blocks while walking the block pointer tree of the pool. Hope I'm correct ;) //Jim ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] [developer] Re: Memory usage concern
(removing developer) On Mon, Oct 15, 2012 at 4:01 PM, Cedric Blancher cedric.blanc...@googlemail.com wrote: On 16 October 2012 00:52, Jason Matthews ja...@broken.net wrote: I should also mention that over all network performance degrades over time and the only fix I have sound so far is to shut down the zones, destroy the vnics, recreate them, and then reboot the zones. I do that about every four hours to keep the response times reasonable. It really sucks. IMO you blame the wrong people. You can have the same kind of problems with any Illumos-based distribution if you activate a zone and let the machine just sit there for a week or so or have a lot filesystem activity using mmap(). Either way the machines will choke themselves to memory starvation. The only workaround we found are regular reboots (every 24h), or limit the ZFS ARC to an absolute minimum. Is this bare-metal or under a VM? We have many mmap()-based workloads running in production, bare-metal, without issue. The ZFS ARC will reduce its size (reap) when the system is low on memory. If it doesn't, and needs workarounds, that's a bug. It can be diagnosed by checking kstats (arcstats, or using arcstat.pl) and using DTrace. And by choke, you mean the system pages out applications, such that you have a rate of anonymous page-ins? Ie, vmstat -p 1 and having a rate of api? A full echo ::kmastat | mdb -k before reboot may show where the memory is or isn't. Brendan -- Brendan Gregg, Joyent http://dtrace.org/blogs/brendan ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] [developer] Re: Memory usage concern
-Original Message-
From: Brendan Gregg [mailto:brendan.gr...@joyent.com]
A full echo ::kmastat | mdb -k before reboot may show where the
memory is or isn't.
I am not a point where I would normally reboot it, but we are pretty well
deep into memory utilization for the size of the apps that run...
On the proxy tier, it seems that the DCE cache is way out of out of line.
What are the tunables here?
Thanks,
j.
Here is a dump from a box on the proxy tier...
root@www003:~# echo ::kmastat |mdb -k |sort -nrk 5 |head
kmem_va_40964096 2964721 2964736 12143558656B 3023570
0
dce_cache152 73389856 73389862 11561725952B 73389938
0
zio_data_buf_131072 131072 43616 43644 5720506368B893451 0
kmem_va_16384 16384 51737 51744 847773696B 51969 0
zio_buf_16384 16384 51386 51475 843366400B 5324046 0
tcp_conn_cache 1808 17352 88512 181272576B 1597914226 0
kmem_va_81928192 22097 22112 181141504B 37356 0
streams_dblk_1040 1152 42 106253 124346368B 1582704292 0
kmem_bufctl_cache 24 3527424 3527541 86519808B 3750227 0
arc_buf_hdr_t176 345516 345576 64339968B 1199529 0
root@www003:~# echo ::memstat |mdb -k
Page SummaryPagesMB %Tot
Kernel3721822 14538 44%
ZFS File Data 1448069 5656 17%
Anon84512 3301%
Exec and libs5085190%
Page cache 15805610%
Free (cachelist)22861890%
Free (freelist) 3072717 12002 37%
Total 8370871 32698
Physical 8370870 32698
And here is one from the database tier...
root@db001:~# echo ::kmastat |mdb -k |sort -nrk 5 |head
zfs_file_data_81928192 2991810 7365904 60341485568B 3495907153 0
kmem_va_4096 4096 4965999 6615520 27097169920B 73888636 0
zio_data_buf_8192 8192 2991120 2991810 24508907520B 3108123433 0
kmem_va_1638416384 216265 1442656 23636475904B 224812598 0
zfs_file_data_buf 24814600192B 24814600192B 24814600192B 15532060657
arc_buf_hdr_t 176 56809623 61605434 11469811712B 489897048 0
zio_buf_131072131072 83335 83370 10927472640B 624255183 0
zio_buf_16384 16384 213952 214677 3517267968B 866096686 0
kmem_alloc_3232 54596040 95296625 3122679808B 4035614613 0
kmem_va_81928192 61443 213888 1752170496B 483211721 0
root@db001:~# echo ::memstat |mdb -k
Page SummaryPagesMB %Tot
Kernel 10971334 42856 44%
ZFS File Data 6059601 23670 24%
Anon 5686726 22213 23%
Exec and libs9304360%
Page cache 53574 2090%
Free (cachelist) 140715 5491%
Free (freelist) 2225873 86949%
Total25147127 98230
Physical 25147125 98230
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] [developer] Re: Memory usage concern
On Mon, Oct 15, 2012 at 5:52 PM, Jason Matthews ja...@broken.net wrote:
-Original Message-
From: Brendan Gregg [mailto:brendan.gr...@joyent.com]
A full echo ::kmastat | mdb -k before reboot may show where the
memory is or isn't.
I am not a point where I would normally reboot it, but we are pretty well
deep into memory utilization for the size of the apps that run...
On the proxy tier, it seems that the DCE cache is way out of out of line.
What are the tunables here?
This sounds like the DCE cache cleanup issue:
http://smartos.org/2012/02/28/using-flamegraph-to-solve-ip-scaling-issue-dce/
A netstat -dn | wc -l should show how many entries are in the cache.
Brendan
Thanks,
j.
Here is a dump from a box on the proxy tier...
root@www003:~# echo ::kmastat |mdb -k |sort -nrk 5 |head
kmem_va_40964096 2964721 2964736 12143558656B 3023570
0
dce_cache152 73389856 73389862 11561725952B 73389938
0
zio_data_buf_131072 131072 43616 43644 5720506368B893451 0
kmem_va_16384 16384 51737 51744 847773696B 51969 0
zio_buf_16384 16384 51386 51475 843366400B 5324046 0
tcp_conn_cache 1808 17352 88512 181272576B 1597914226 0
kmem_va_81928192 22097 22112 181141504B 37356 0
streams_dblk_1040 1152 42 106253 124346368B 1582704292 0
kmem_bufctl_cache 24 3527424 3527541 86519808B 3750227
0
arc_buf_hdr_t176 345516 345576 64339968B 1199529 0
root@www003:~# echo ::memstat |mdb -k
Page SummaryPagesMB %Tot
Kernel3721822 14538 44%
ZFS File Data 1448069 5656 17%
Anon84512 3301%
Exec and libs5085190%
Page cache 15805610%
Free (cachelist)22861890%
Free (freelist) 3072717 12002 37%
Total 8370871 32698
Physical 8370870 32698
--
Brendan Gregg, Joyent http://dtrace.org/blogs/brendan
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Boot stalls on install
Hello all... I'm trying to boot from DVD to install Opeindiana on a Gigabyte H55M-S2V and Im having issues. As soon as I get past the grub screen and select boot from cd I get the oracle trademark message and everything freezes up. My keyboars (regualr ps2 connection) becomes unusable and I have to hard boot. It's an Intell H55 express chipset and the memory is seated fiine and I've switched out sticks to ensure I don't have a RAM issue. FreeBSD seems to boot up fine so I know hardware doesn't seem to be an issue. I'd rather use Openindiana if I can help it instead of FreeBSD. Has asyone tried installing on this chipset before? ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ZFS, Samba, Windows ACLs
Date: Sat, 13 Oct 2012 19:01:43 +0400 From: Jim Klimov jimkli...@cos.ru To: Discussion list for OpenIndiana openindiana-discuss@openindiana.org Subject: Re: [OpenIndiana-discuss] ZFS, Samba, Windows ACLs Message-ID: 50798257.6050...@cos.ru Content-Type: text/plain; charset=ISO-8859-1; format=flowed 2012-10-13 1:51, lbr...@me.com wrote: I have used this site in the past (http://www.nineproductions.com/solaris-11-samba-zfs-configuration/) to configure a solaris server for Samba and windows ACLs and it worked pretty well. I am trying the same on OpenIndiana and cannot seem to get it to work. Are there any good tutorials out there for this? (I did google and could not find any)? Specifically the issues are with PAM, nsswitch, and setting the ACLs. -svccfg -s name-service/switch --svccfg: Pattern 'name-service/switch' doesn't match any instances or services Nsswitch does not seem to exist. (Remember I am new to this and it may be staring me in the face.) First of all, this should be all with dashes (at least in OI): # svccfg -s name-service-switch Tried this and same issue, not found. I did try a `pkg search` but could not find the package. Not sure what I am doing wrong... :/ Also there are name-services (when changing naming configs, you often are better off restarting both of these). And, -chmod A- /tank1/Data --Try `chmod --help' for more information. So the chmod accepts options in a different manner. I read the help page but was still lost. As others said, make sure to use /usr/bin/chmod. //Jim /usr/bin/chmod was what I was looking for! Thanks! ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Boot stalls on install
From: dbent...@nas.edu To: openindiana-discuss@openindiana.org Date: Mon, 15 Oct 2012 22:02:05 -0400 Subject: [OpenIndiana-discuss] Boot stalls on install Hello all... I'm trying to boot from DVD to install Opeindiana on a Gigabyte H55M-S2V and Im having issues. As soon as I get past the grub screen and select boot from cd I get the oracle trademark message and everything freezes up. My keyboars (regualr ps2 connection) becomes unusable and I have to hard boot. It's an Intell H55 express chipset and the memory is seated fiine and I've switched out sticks to ensure I don't have a RAM issue. FreeBSD seems to boot up fine so I know hardware doesn't seem to be an issue. I'd rather use Openindiana if I can help it instead of FreeBSD. Has asyone tried installing on this chipset before? I'm not using that chipset, but as the next step, you could try booting with more logging on. Clear out the graphics parts from grub and add the kernel options as below. 'e' allows you to edit a line. You'll want the section to look similar to below (hoping my VBox setup is similar enough): kernel$ /platform/i86pc/kernel/$ISADIR/unix -s -v -k module$ /platform/i86pc/$ISADIR/boot_archive then hit 'b' to boot from the modified entries. -s means single user mode; -v means verbose, and -k means kernel debugger land if something does bomb. Hopefully that may point to a driver that may be having issues or otherwise narrow down what is going on. Hth, Nathan ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] I am having problems with Inkscape and convert producing PNG's
Hi, On po, 2012-10-15 at 12:12 -0500, Bob Friesenhahn wrote: On Mon, 15 Oct 2012, Jonathan Adams wrote: it's the same message on both, I'm not sure if Inkscape is using convert to produce the file. jadams@jadlaptop:~/images$ convert Mylogo.svg /tmp/Mylogo.png convert: Application was compiled with png.h from libpng-1.2.44 `/tmp/Mylogo.png' @ warning/png.c/MagickPNGWarningHandler/1781. convert: Application is running with png.c from libpng-1.4.3 `/tmp/Mylogo.png' @ warning/png.c/MagickPNGWarningHandler/1781. convert: Incompatible libpng version in application and library `/tmp/Mylogo.png' @ warning/png.c/MagickPNGWarningHandler/1781. convert: memory allocation failed `/tmp/Mylogo.png' @ error/png.c/WriteOnePNGImage/8873. jadams@jadlaptop:/sal/images$ pkg list | egrep -i inkscape|png|magick image/editor/imagemagick (sfe)6.7.6.10-0.151.1.5 i-- image/editor/inkscape (sfe) 0.48.2-0.151.1.5 i-- image/library/g++/imagemagick (sfe) 6.7.6.10-0.151.1.5 i-- image/library/libpng 0.5.11-0.151.1.7 i-- SFE ImageMagick has a bug and this should be reported to the OpenIndiana SFE bug tracker. The bug can be illustrated by executing 'convert -list format' and looking at the details for PNG: PNG* PNG rw- Portable Network Graphics (libpng 1.2.44,1.4.3) See http://www.libpng.org/ for details about the PNG format. What the error messages and the PNG detail information is telling us is that the png headers used do not match the png library used. Bob It is known bug - https://www.illumos.org/issues/2706 Currently I spend time updating JDS and not in fight with bloody libpng. My vision is to build everything in JDS with libpng 1.4, to solve all these problems. If anybody has time for fixing SFE ImageMagick to build with older libpng temporarily then he is welcome to prepare fix and I can push the results to the repository :-) Best regards, Milan ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
