devil-linux-discuss — General Mailing List for all discussions

[Devil-Linux-discuss] httpd and DL 1.4.2 was:Re: System-Crash with SMP

[Udo L. <udo...@al...>]

Hi Heiko,
i have done a new test with the 1.4.2 and apache but no luck:
Jan 28 18:36:23 src@localhost kernel: : httpd[6181]: segfault at 
af6ccecc ip af6b7b92 sp baf3891c error 7 in ld-2.10.1.so[af6b1000+1b000]
Jan 28 18:36:23 src@localhost kernel: : grsec: Segmentation fault 
occurred at af6ccecc in /usr/sbin/httpd[httpd:6181] uid/euid:0/0 
gid/egid:0/0, parent /sbin/init[init:1] ui

So I'm back on 1.4-i686! :-(

Ther are nothing (i think so) special in the httpd.conf:

PidFile /var/run/httpd.pid
Listen 127.0.0.1:8080
LoadModule authn_file_module /usr/lib/apache2/modules/mod_authn_file.so
LoadModule authn_dbm_module /usr/lib/apache2/modules/mod_authn_dbm.so
LoadModule authn_anon_module /usr/lib/apache2/modules/mod_authn_anon.so
LoadModule authn_dbd_module /usr/lib/apache2/modules/mod_authn_dbd.so
LoadModule authn_default_module 
/usr/lib/apache2/modules/mod_authn_default.so
LoadModule authz_host_module /usr/lib/apache2/modules/mod_authz_host.so
LoadModule authz_groupfile_module 
/usr/lib/apache2/modules/mod_authz_groupfile.so
LoadModule authz_user_module /usr/lib/apache2/modules/mod_authz_user.so
LoadModule authz_dbm_module /usr/lib/apache2/modules/mod_authz_dbm.so
LoadModule authz_owner_module /usr/lib/apache2/modules/mod_authz_owner.so
LoadModule authz_default_module 
/usr/lib/apache2/modules/mod_authz_default.so
LoadModule auth_basic_module /usr/lib/apache2/modules/mod_auth_basic.so
LoadModule auth_digest_module /usr/lib/apache2/modules/mod_auth_digest.so
LoadModule file_cache_module /usr/lib/apache2/modules/mod_file_cache.so
LoadModule cache_module /usr/lib/apache2/modules/mod_cache.so
LoadModule disk_cache_module /usr/lib/apache2/modules/mod_disk_cache.so
LoadModule mem_cache_module /usr/lib/apache2/modules/mod_mem_cache.so
LoadModule bucketeer_module /usr/lib/apache2/modules/mod_bucketeer.so
LoadModule dumpio_module /usr/lib/apache2/modules/mod_dumpio.so
LoadModule case_filter_module /usr/lib/apache2/modules/mod_case_filter.so
LoadModule case_filter_in_module 
/usr/lib/apache2/modules/mod_case_filter_in.so
LoadModule ext_filter_module /usr/lib/apache2/modules/mod_ext_filter.so
LoadModule include_module /usr/lib/apache2/modules/mod_include.so
LoadModule filter_module /usr/lib/apache2/modules/mod_filter.so
LoadModule substitute_module /usr/lib/apache2/modules/mod_substitute.so
LoadModule deflate_module /usr/lib/apache2/modules/mod_deflate.so
LoadModule log_config_module /usr/lib/apache2/modules/mod_log_config.so
LoadModule log_forensic_module /usr/lib/apache2/modules/mod_log_forensic.so
LoadModule logio_module /usr/lib/apache2/modules/mod_logio.so
LoadModule env_module /usr/lib/apache2/modules/mod_env.so
LoadModule mime_magic_module /usr/lib/apache2/modules/mod_mime_magic.so
LoadModule cern_meta_module /usr/lib/apache2/modules/mod_cern_meta.so
LoadModule expires_module /usr/lib/apache2/modules/mod_expires.so
LoadModule headers_module /usr/lib/apache2/modules/mod_headers.so
LoadModule ident_module /usr/lib/apache2/modules/mod_ident.so
LoadModule usertrack_module /usr/lib/apache2/modules/mod_usertrack.so
LoadModule unique_id_module /usr/lib/apache2/modules/mod_unique_id.so
LoadModule setenvif_module /usr/lib/apache2/modules/mod_setenvif.so
LoadModule version_module /usr/lib/apache2/modules/mod_version.so
LoadModule proxy_module /usr/lib/apache2/modules/mod_proxy.so
LoadModule proxy_connect_module 
/usr/lib/apache2/modules/mod_proxy_connect.so
LoadModule proxy_ftp_module /usr/lib/apache2/modules/mod_proxy_ftp.so
LoadModule proxy_http_module /usr/lib/apache2/modules/mod_proxy_http.so
LoadModule proxy_scgi_module /usr/lib/apache2/modules/mod_proxy_scgi.so
LoadModule proxy_ajp_module /usr/lib/apache2/modules/mod_proxy_ajp.so
LoadModule proxy_balancer_module 
/usr/lib/apache2/modules/mod_proxy_balancer.so
LoadModule ssl_module /usr/lib/apache2/modules/mod_ssl.so
LoadModule mime_module /usr/lib/apache2/modules/mod_mime.so
LoadModule dav_module /usr/lib/apache2/modules/mod_dav.so
LoadModule status_module /usr/lib/apache2/modules/mod_status.so
LoadModule autoindex_module /usr/lib/apache2/modules/mod_autoindex.so
LoadModule asis_module /usr/lib/apache2/modules/mod_asis.so
LoadModule info_module /usr/lib/apache2/modules/mod_info.so
LoadModule suexec_module /usr/lib/apache2/modules/mod_suexec.so
LoadModule cgi_module /usr/lib/apache2/modules/mod_cgi.so
LoadModule cgid_module /usr/lib/apache2/modules/mod_cgid.so
LoadModule dav_fs_module /usr/lib/apache2/modules/mod_dav_fs.so
LoadModule dav_lock_module /usr/lib/apache2/modules/mod_dav_lock.so
LoadModule vhost_alias_module /usr/lib/apache2/modules/mod_vhost_alias.so
LoadModule negotiation_module /usr/lib/apache2/modules/mod_negotiation.so
LoadModule dir_module /usr/lib/apache2/modules/mod_dir.so
LoadModule imagemap_module /usr/lib/apache2/modules/mod_imagemap.so
LoadModule actions_module /usr/lib/apache2/modules/mod_actions.so
LoadModule speling_module /usr/lib/apache2/modules/mod_speling.so
LoadModule userdir_module /usr/lib/apache2/modules/mod_userdir.so
LoadModule alias_module /usr/lib/apache2/modules/mod_alias.so
LoadModule rewrite_module /usr/lib/apache2/modules/mod_rewrite.so
LoadModule php5_module        /usr/lib/apache2/modules/libphp5.so
<IfModule !mpm_netware_module>
<IfModule !mpm_winnt_module>
User nobody
Group nogroup
</IfModule>
</IfModule>
ServerAdmin su...@xx...
DocumentRoot "/usr/share/apache2/default-site/htdocs"
<Directory />
     Options FollowSymLinks
     AllowOverride None
     Order deny,allow
     Deny from all
</Directory>
<Directory "/usr/share/apache2/default-site/htdocs">
     Options Indexes FollowSymLinks
     AllowOverride None
     Order allow,deny
     Allow from all
</Directory>
<IfModule dir_module>
     DirectoryIndex index.html index.php login.php
</IfModule>
<FilesMatch "^\.ht">
     Order allow,deny
     Deny from all
     Satisfy All
</FilesMatch>
ErrorLog "/var/data/www/xxx.com/log/apache_error_log"
LogLevel warn
<IfModule log_config_module>
     LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" 
\"%{User-Agent}i\"" combined
     LogFormat "%h %l %u %t \"%r\" %>s %b" common
<IfModule logio_module>
       LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" 
\"%{User-Agent}i\" %I %O" combinedio
</IfModule>
     CustomLog "/var/log/apache2/access_log" common
</IfModule>
<IfModule alias_module>
     ScriptAlias /cgi-bin/ "/usr/lib/cgi-bin/"
</IfModule>
<IfModule cgid_module>
</IfModule>
<Directory "/usr/lib/cgi-bin">
     AllowOverride None
     Options None
     Order allow,deny
     Allow from all
</Directory>
DefaultType text/plain
AddType application/x-httpd-php .php .php4 .php3 .phtml
<IfModule mime_module>
     TypesConfig /etc/apache2/mime.types
     AddType application/x-compress .Z
     AddType application/x-gzip .gz .tgz
</IfModule>
EnableMMAP off
EnableSendfile off
Include /etc/apache2/extra/httpd-vhosts.conf
<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>

# vhosts:
NameVirtualHost *:8080
<VirtualHost *:8080>
     ServerAdmin su...@xx...
     DocumentRoot "/var/data/www/xxx.com/web"
     ServerName xxx.com
     ErrorLog "/var/data/www/xxx.com/log/xxx.com-error_log"
     CustomLog "/var/data/www/xxx.com/log/xxx.com-access_log" common
</VirtualHost>
<Directory "/var/data/www/xxx.com/web/pma">
     AuthType Basic
     AuthName "Protected Area"
     AuthBasicProvider file
     AuthUserFile /etc/apache2/authentication/passwords
     Require valid-user
     Deny from all
     Satisfy Any
</Directory>
<Directory "/var/data/www/xxx.com">
     Options -Indexes FollowSymLinks
     AllowOverride None
     Order allow,deny
     Allow from all
</Directory>

##########################################

best regards

Udo



Am 20.01.2011 16:00, schrieb Heiko Zuerker:
>
> Quoting xy zy<big...@fr...>:
>
>    
>> I tested it, and it's working. (1.4.2-i686)
>>
>> I'm waiting for new version. (updates shorewall)
>>      
>   I'm uploading the latest test build. It should be done about 30 minutes after this email was sent.
>
>    

Re: [Devil-Linux-discuss] DL as virtualization platform

[Serge L. <ser...@gm...>]

Hello,

DL_64 ( which is designed to be a KVM-based host machine ) has been uploaded to 
olga.mooo.com

kernel 3.6.37, also I've added  support for sheepdog storage cluster to kvmctl.
There are also btrfs and snapshot merge capable LVM2.

PS. It's a research project, the result will be merged to DL eventually but now 
it's something like a separate branch.

Serge

Re: [Devil-Linux-discuss] DL as virtualisation platform

[Motycka J. <mai...@vc...>]

Ohh yes.
Quite obscure but cool solution :). I will try to setup this 
architecture and try its functionality.
Thanks for hint :).

Jiri


-------- Původní zpráva --------
Předmět: Re: [Devil-Linux-discuss] DL as virtualisation platform
Od: Serge Leschinsky <ser...@gm...>
Komu: dev...@li...
Datum: 24.1.2011 22:28
> The good thing is you can test it anyway :) Bring 3 DL images up from on your 
> machine for kvm and configure sheepdog cluster on them. Since it's just an 
> network cloud, all other VMs can be started from this virtualized cluster. And, 
> actually, sheepdog-cluster can be created on any machines (not only on 
> kvm-capable) - it's just 2 user-space daemons.
>
> It's not a production mode though.
>
> Serge
>
> On 01/24/2011 12:49 PM, Motycka Jiri wrote:
>   
>> Thank you very much :).
>> I have studied Sheepdog project. It is very interesting idea, byt I
>> haven't no more than 1 machine for kvm virtualisation, and it is not
>> enought to test sheepdog in true function.
>>
>> Jiri
>>
>>     
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
> February 28th, so secure your free ArcSight Logger TODAY! 
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>   

Re: [Devil-Linux-discuss] DL as virtualisation platform

[Serge L. <ser...@gm...>]

The good thing is you can test it anyway :) Bring 3 DL images up from on your 
machine for kvm and configure sheepdog cluster on them. Since it's just an 
network cloud, all other VMs can be started from this virtualized cluster. And, 
actually, sheepdog-cluster can be created on any machines (not only on 
kvm-capable) - it's just 2 user-space daemons.

It's not a production mode though.

Serge

On 01/24/2011 12:49 PM, Motycka Jiri wrote:
> Thank you very much :).
> I have studied Sheepdog project. It is very interesting idea, byt I
> haven't no more than 1 machine for kvm virtualisation, and it is not
> enought to test sheepdog in true function.
>
> Jiri
>

Re: [Devil-Linux-discuss] DL as virtualisation platform

[Motycka J. <mai...@vc...>]

Thank you very much :).
I have studied Sheepdog project. It is very interesting idea, byt I 
haven't no more than 1 machine for kvm virtualisation, and it is not 
enought to test sheepdog in true function.

Jiri


-------- Původní zpráva --------
Předmět: Re: [Devil-Linux-discuss] DL as virtualisation platform
Od: Serge Leschinsky <ser...@gm...>
Komu: dev...@li...
Kopie: Jiri Motycka <mai...@vc...>
Datum: 24.1.2011 06:46
> Jiri,
>
> yes, I think it's possible. I work on 2.6.37 now - and I think 
> 2.6.36.x should not be a problem either.
>
> PS. Happy to know that it works for you! Did you try sheepdog? It 
> works perfectly. I'm going to add init scripts for corosync and 
> sheepdog, then sheepdog-cluster support to kvmctl.
>
> Serge
>
> On 01/23/2011 02:39 PM, Jiri Motycka wrote:
>> Hello, is it possible to compile bootcd.iso from this link
>> (ftp://olga.mooo.com/DL_64/bootcd.iso) with kernel 2.6.36.3 or newer
>> (insted of 2.3.35.10). There would be a support for new set of intel
>> gigabit network cards (82579) from this release.
>>
>> Jiri
>>
>> ps.: for me, kvm from actual release works great :).
>>
>>
>> Serge Leschinsky napsal(a):
>>> Hello,
>>>
>>> unfortunately, the kernel I used is not good. See details here:
>>> https://bugzilla.kernel.org/show_bug.cgi?id=16588
>>>
>>> So,  if your kernel is "freezing, crashing, oopsing" please download 
>>> a new image
>>> with updated kernel.
>>>
>>> PS. The image is a bit heavier because I added several packages to 
>>> test.
>>>
>>> Serge
>>>
>>> On 08/19/2010 04:44 PM, Serge Leschinsky wrote:
>>>> Hello,
>>>>
>>>> I have updated ISO - KVM works fine, Sheepdog has been incorporated 
>>>> but not tested.
>>>>
>>>> ftp://olga.mooo.com/DL_64/bootcd.iso
>>>>
>>>>    129M Aug 19 16:35 bootcd.iso
>>>>      45 Aug 19 16:37 bootcd.iso.md5
>>>>
>>>>
>>>> Serge
>>>>
>>>>
>>>> On 08/01/2010 07:57 PM, Serge Leschinsky wrote:
>>>>> Hi Jiri,
>>>>>
>>>>> You can download the test image from ftp://olga.mooo.com/DL_64
>>>>>
>>>>> Please feel free to ask me directly in case of any problems. I've 
>>>>> included init
>>>>> script and a VM template (/etc/kvm/* ) to simplify the first step. 
>>>>> Please use
>>>>> kvmctl tool to manage your VMs.
>>>>>
>>>>> Sheepdog is not incorporated, but I'm going to do it.
>>>>>
>>>>> Serge
>>>>>
>>>>>
>>>>> On 07/27/2010 12:39 AM, Motycka Jiri wrote:
>>>>>> Hello.
>>>>>>
>>>>>> Thank you very much. Your ansver makes me happy :-).
>>>>>> You can count with me as a tester. But at first I must get some
>>>>>> information about KVM on my own, because I have never met KVM 
>>>>>> before.
>>>>>>
>>>>>> Jiri
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> -------- Původní zpráva --------
>>>>>> Předmět: Re: [Devil-Linux-discuss] DL as virtualisation platform
>>>>>> Od: Serge Leschinsky<fi...@in...>
>>>>>> Komu: dev...@li...
>>>>>> Datum: 22.7.2010 20:32
>>>>>>> Hi Jiri,
>>>>>>>
>>>>>>> it's a good idea, but I'd rather do it with KVM :) because it's 
>>>>>>> a mainstream,
>>>>>>> sheepdog (a distributed storage system) will be available soon etc
>>>>>>>
>>>>>>> The requirement is 64bit DL, which is actually in alpha. If you 
>>>>>>> wish tobe a
>>>>>>> tester, you are very welcome.
>>>>>>>
>>>>>>> Unfortunately, I have no time to play with KVM on DL, but I've 
>>>>>>> compiledit.
>>>>>>> Maybe it works.
>>>>>>>
>>>>>>> Serge
>>>>>>>
>>>>>>> On 07/22/2010 02:31 AM, Motycka Jiri wrote:
>>>>>>>
>>>>>>>> Hello DL community.
>>>>>>>>
>>>>>>>> I have got an idea. What about making DL as a small virtualisation
>>>>>>>> platform. Tool for this could be VirtualBox OSE.
>>>>>>>> With couple of benefits of DL (genial system of booting, 
>>>>>>>> configuring, sw
>>>>>>>> raid support, lvm) it could be very useful (I think).
>>>>>>>> I would like to try to compile VirtualBox OSE HeadLess to DL, 
>>>>>>>> but I am
>>>>>>>> totaly unexperienced in it. And my tries ended just at start :(.
>>>>>>>>
>>>>>>>> What do you think about it ?
>>>>>>>> Is there anybody skilled to compile Virtualbox OSE Headless to 
>>>>>>>> DL ?
>>>>>>>>
>>>>>>>>
>>>>>>>> Jiri Motycka
>>>> ------------------------------------------------------------------------------ 
>>>>
>>>> This SF.net email is sponsored by
>>>>
>>>> Make an app they can't live without
>>>> Enter the BlackBerry Developer Challenge
>>>> http://p.sf.net/sfu/RIM-dev2dev
>>>> _______________________________________________
>>>> Devil-linux-discuss mailing list
>>>> Dev...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>>>
>>> ------------------------------------------------------------------------------ 
>>>
>>> This SF.net email is sponsored by
>>>
>>> Make an app they can't live without
>>> Enter the BlackBerry Developer Challenge
>>> http://p.sf.net/sfu/RIM-dev2dev
>>> _______________________________________________
>>> Devil-linux-discuss mailing list
>>> Dev...@li...
>>> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>>
>>
>> ------------------------------------------------------------------------------ 
>>
>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
>> Finally, a world-class log management solution at an even better 
>> price-free!
>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
>> February 28th, so secure your free ArcSight Logger TODAY!
>> http://p.sf.net/sfu/arcsight-sfd2d
>> _______________________________________________
>> Devil-linux-discuss mailing list
>> Dev...@li...
>> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>

Re: [Devil-Linux-discuss] DL as virtualisation platform

[Serge L. <ser...@gm...>]

Jiri,

yes, I think it's possible. I work on 2.6.37 now - and I think 2.6.36.x should 
not be a problem either.

PS. Happy to know that it works for you! Did you try sheepdog? It works 
perfectly. I'm going to add init scripts for corosync and sheepdog, then 
sheepdog-cluster support to kvmctl.

Serge

On 01/23/2011 02:39 PM, Jiri Motycka wrote:
> Hello, is it possible to compile bootcd.iso from this link
> (ftp://olga.mooo.com/DL_64/bootcd.iso) with kernel 2.6.36.3 or newer
> (insted of 2.3.35.10). There would be a support for new set of intel
> gigabit network cards (82579) from this release.
>
> Jiri
>
> ps.: for me, kvm from actual release works great :).
>
>
> Serge Leschinsky napsal(a):
>> Hello,
>>
>> unfortunately, the kernel I used is not good. See details here:
>> https://bugzilla.kernel.org/show_bug.cgi?id=16588
>>
>> So,  if your kernel is "freezing, crashing, oopsing" please download a new image
>> with updated kernel.
>>
>> PS. The image is a bit heavier because I added several packages to test.
>>
>> Serge
>>
>> On 08/19/2010 04:44 PM, Serge Leschinsky wrote:
>>> Hello,
>>>
>>> I have updated ISO - KVM works fine, Sheepdog has been incorporated but not tested.
>>>
>>> ftp://olga.mooo.com/DL_64/bootcd.iso
>>>
>>>    129M Aug 19 16:35 bootcd.iso
>>>      45 Aug 19 16:37 bootcd.iso.md5
>>>
>>>
>>> Serge
>>>
>>>
>>> On 08/01/2010 07:57 PM, Serge Leschinsky wrote:
>>>> Hi Jiri,
>>>>
>>>> You can download the test image from ftp://olga.mooo.com/DL_64
>>>>
>>>> Please feel free to ask me directly in case of any problems. I've included init
>>>> script and a VM template (/etc/kvm/* ) to simplify the first step. Please use
>>>> kvmctl tool to manage your VMs.
>>>>
>>>> Sheepdog is not incorporated, but I'm going to do it.
>>>>
>>>> Serge
>>>>
>>>>
>>>> On 07/27/2010 12:39 AM, Motycka Jiri wrote:
>>>>> Hello.
>>>>>
>>>>> Thank you very much. Your ansver makes me happy :-).
>>>>> You can count with me as a tester. But at first I must get some
>>>>> information about KVM on my own, because I have never met KVM before.
>>>>>
>>>>> Jiri
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> -------- Původní zpráva --------
>>>>> Předmět: Re: [Devil-Linux-discuss] DL as virtualisation platform
>>>>> Od: Serge Leschinsky<fi...@in...>
>>>>> Komu: dev...@li...
>>>>> Datum: 22.7.2010 20:32
>>>>>> Hi Jiri,
>>>>>>
>>>>>> it's a good idea, but I'd rather do it with KVM :) because it's a mainstream,
>>>>>> sheepdog (a distributed storage system) will be available soon etc
>>>>>>
>>>>>> The requirement is 64bit DL, which is actually in alpha. If you wish tobe a
>>>>>> tester, you are very welcome.
>>>>>>
>>>>>> Unfortunately, I have no time to play with KVM on DL, but I've compiledit.
>>>>>> Maybe it works.
>>>>>>
>>>>>> Serge
>>>>>>
>>>>>> On 07/22/2010 02:31 AM, Motycka Jiri wrote:
>>>>>>
>>>>>>> Hello DL community.
>>>>>>>
>>>>>>> I have got an idea. What about making DL as a small virtualisation
>>>>>>> platform. Tool for this could be VirtualBox OSE.
>>>>>>> With couple of benefits of DL (genial system of booting, configuring, sw
>>>>>>> raid support, lvm) it could be very useful (I think).
>>>>>>> I would like to try to compile VirtualBox OSE HeadLess to DL, but I am
>>>>>>> totaly unexperienced in it. And my tries ended just at start :(.
>>>>>>>
>>>>>>> What do you think about it ?
>>>>>>> Is there anybody skilled to compile Virtualbox OSE Headless to DL ?
>>>>>>>
>>>>>>>
>>>>>>> Jiri Motycka
>>> ------------------------------------------------------------------------------
>>> This SF.net email is sponsored by
>>>
>>> Make an app they can't live without
>>> Enter the BlackBerry Developer Challenge
>>> http://p.sf.net/sfu/RIM-dev2dev
>>> _______________________________________________
>>> Devil-linux-discuss mailing list
>>> Dev...@li...
>>> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by
>>
>> Make an app they can't live without
>> Enter the BlackBerry Developer Challenge
>> http://p.sf.net/sfu/RIM-dev2dev
>> _______________________________________________
>> Devil-linux-discuss mailing list
>> Dev...@li...
>> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss

Re: [Devil-Linux-discuss] DL as virtualisation platform

[Jiri M. <mai...@vc...>]

Hello, is it possible to compile bootcd.iso from this link 
(ftp://olga.mooo.com/DL_64/bootcd.iso) with kernel 2.6.36.3 or newer 
(insted of 2.3.35.10). There would be a support for new set of intel 
gigabit network cards (82579) from this release.

Jiri

ps.: for me, kvm from actual release works great :).


Serge Leschinsky napsal(a):
> Hello,
>
> unfortunately, the kernel I used is not good. See details here:
> https://bugzilla.kernel.org/show_bug.cgi?id=16588
>
> So,  if your kernel is "freezing, crashing, oopsing" please download a new image
> with updated kernel.
>
> PS. The image is a bit heavier because I added several packages to test.
>
> Serge
>
> On 08/19/2010 04:44 PM, Serge Leschinsky wrote:
>> Hello,
>>
>> I have updated ISO - KVM works fine, Sheepdog has been incorporated but not tested.
>>
>> ftp://olga.mooo.com/DL_64/bootcd.iso
>>
>>   129M Aug 19 16:35 bootcd.iso
>>     45 Aug 19 16:37 bootcd.iso.md5
>>
>>
>> Serge
>>
>>
>> On 08/01/2010 07:57 PM, Serge Leschinsky wrote:
>>> Hi Jiri,
>>>
>>> You can download the test image from ftp://olga.mooo.com/DL_64
>>>
>>> Please feel free to ask me directly in case of any problems. I've included init
>>> script and a VM template (/etc/kvm/* ) to simplify the first step. Please use
>>> kvmctl tool to manage your VMs.
>>>
>>> Sheepdog is not incorporated, but I'm going to do it.
>>>
>>> Serge
>>>
>>>
>>> On 07/27/2010 12:39 AM, Motycka Jiri wrote:
>>>> Hello.
>>>>
>>>> Thank you very much. Your ansver makes me happy :-).
>>>> You can count with me as a tester. But at first I must get some
>>>> information about KVM on my own, because I have never met KVM before.
>>>>
>>>> Jiri
>>>>
>>>>
>>>>
>>>>
>>>> -------- Původní zpráva --------
>>>> Předmět: Re: [Devil-Linux-discuss] DL as virtualisation platform
>>>> Od: Serge Leschinsky<fi...@in...>
>>>> Komu: dev...@li...
>>>> Datum: 22.7.2010 20:32
>>>>> Hi Jiri,
>>>>>
>>>>> it's a good idea, but I'd rather do it with KVM :) because it's a mainstream,
>>>>> sheepdog (a distributed storage system) will be available soon etc
>>>>>
>>>>> The requirement is 64bit DL, which is actually in alpha. If you wish tobe a
>>>>> tester, you are very welcome.
>>>>>
>>>>> Unfortunately, I have no time to play with KVM on DL, but I've compiledit.
>>>>> Maybe it works.
>>>>>
>>>>> Serge
>>>>>
>>>>> On 07/22/2010 02:31 AM, Motycka Jiri wrote:
>>>>>
>>>>>> Hello DL community.
>>>>>>
>>>>>> I have got an idea. What about making DL as a small virtualisation
>>>>>> platform. Tool for this could be VirtualBox OSE.
>>>>>> With couple of benefits of DL (genial system of booting, configuring, sw
>>>>>> raid support, lvm) it could be very useful (I think).
>>>>>> I would like to try to compile VirtualBox OSE HeadLess to DL, but I am
>>>>>> totaly unexperienced in it. And my tries ended just at start :(.
>>>>>>
>>>>>> What do you think about it ?
>>>>>> Is there anybody skilled to compile Virtualbox OSE Headless to DL ?
>>>>>>
>>>>>>
>>>>>> Jiri Motycka
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by
>>
>> Make an app they can't live without
>> Enter the BlackBerry Developer Challenge
>> http://p.sf.net/sfu/RIM-dev2dev
>> _______________________________________________
>> Devil-linux-discuss mailing list
>> Dev...@li...
>> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss

Re: [Devil-Linux-discuss] Samba wide links problems: canonicalize_connect_path failed

[Dominic R. <dl...@ed...>]

On 23/01/11 14:35, Heiko Zuerker wrote:
> Quoting Dominic Raferd<dl...@ed...>:
>
>> On 22/01/11 20:20, Heiko Zuerker wrote:
>>> Quoting Dominic Raferd<dl...@ed...>:
>>>> On 22/01/11 12:06, Heiko Zuerker wrote:
>>>>> Quoting Dominic Raferd<dl...@ed...>:
>>>>>
>>>>>> On 22/01/11 11:45, Heiko Zuerker wrote:
>>>>>>> Quoting Dominic Raferd<dl...@ed...>:
>>>>>>>> Thanks Heiko, but I do not have /var anywhere in my smb.conf file. I
>>>>>>>> only have paths that are subdirectories of /home.
>>>>>>> Okay.
>>>>>>>
>>>>>>> Do you have this line in the smb.conf?
>>>>>>>
>>>>>>> [IPC$]
>>>>>>> wide links = Yes
>>>>>>>
>>>>>> No, I have no reference to IPC at all. I think IPC is some internal
>>>>>> Samba thingy. I do have 'wide links = Yes' in all my shares (but IPC is
>>>>>> not among them) - I want to have wide links = No (the default - safe -
>>>>>> setting) but this prevents access.
>>>>> Add the above 2 lines to your smb.conf and things should work better.
>>>>> It's a hidden share which is being used for the communication.
>>>>> (Not sure about the details on it).
>>>> If I add lines:
>>>>
>>>> [IPC$]
>>>>        path = /shm/var/tmp
>>>>        wide links = Yes
>>>>
>>>> then the errors in log about IPC stop, which is good, thanks. Both of
>>>> these lines are needed. But if I have a share with wide links = No and I
>>>> try to connect to it I still see this in the log:
>>>>
>>>> [2011/01/22 14:27:18.361834,  0] smbd/service.c:988(make_connection_snum)
>>>>      canonicalize_connect_path failed for service exampleshare, path
>>>> /home/z-shares/exampleshare
>>> I don't understand why it fails on /home, the ones I used under /var
>>> were explained by the symlink.
>>>
>> And it not only fails on /home, it also fails with shares on /var or
>> /shm/var... The only way I can get it to work is with 'wide links = Yes'
>> parameter. In fact I cannot find any location that works with 'wide
>> links = no'. Do you have shares on /var working with 'wide links = No'?
> No.
> wide links = yes used to be the default on Samba, but they changed it.
> That's why it's failing all the sudden.
Yes, when I first ran 1.4.1 it broke everything until I realised this 
(and added 'wide links = no')
> It has to do with the symlinks we're using.
> One thing you can try is pointing TMP to a different location before
> you start samba, so that there's no symlink being used (i.e. /shm/tmp
> ). I did a lot of trial and error when I analyzed it first. Don't
> remember all the things I did.
You mean something like:
# export TMP=/shm/var/tmp
# /etc/init.d/samba restart
? I tried this (and also for TEMP and TMPDIR) but no joy :-(
> I'm planning to not use many symlinks in the next major DL release,
> but rather use the "bind" feature of mount. This should help prevent
> problems like this.
Sounds good, I will look forward to it - but I know it may be a while :-)

Dominic

Re: [Devil-Linux-discuss] Samba wide links problems: canonicalize_connect_path failed

[Heiko Z. <he...@zu...>]

Quoting Dominic Raferd <dl...@ed...>:

> On 22/01/11 20:20, Heiko Zuerker wrote:
>> Quoting Dominic Raferd<dl...@ed...>:
>>> On 22/01/11 12:06, Heiko Zuerker wrote:
>>>> Quoting Dominic Raferd<dl...@ed...>:
>>>>
>>>>> On 22/01/11 11:45, Heiko Zuerker wrote:
>>>>>> Quoting Dominic Raferd<dl...@ed...>:
>>>>>>> Thanks Heiko, but I do not have /var anywhere in my smb.conf file. I
>>>>>>> only have paths that are subdirectories of /home.
>>>>>> Okay.
>>>>>>
>>>>>> Do you have this line in the smb.conf?
>>>>>>
>>>>>> [IPC$]
>>>>>> wide links = Yes
>>>>>>
>>>>> No, I have no reference to IPC at all. I think IPC is some internal
>>>>> Samba thingy. I do have 'wide links = Yes' in all my shares (but IPC is
>>>>> not among them) - I want to have wide links = No (the default - safe -
>>>>> setting) but this prevents access.
>>>> Add the above 2 lines to your smb.conf and things should work better.
>>>> It's a hidden share which is being used for the communication.
>>>> (Not sure about the details on it).
>>> If I add lines:
>>>
>>> [IPC$]
>>>       path = /shm/var/tmp
>>>       wide links = Yes
>>>
>>> then the errors in log about IPC stop, which is good, thanks. Both of
>>> these lines are needed. But if I have a share with wide links = No and I
>>> try to connect to it I still see this in the log:
>>>
>>> [2011/01/22 14:27:18.361834,  0] smbd/service.c:988(make_connection_snum)
>>>     canonicalize_connect_path failed for service exampleshare, path
>>> /home/z-shares/exampleshare
>> I don't understand why it fails on /home, the ones I used under /var
>> were explained by the symlink.
>>
> And it not only fails on /home, it also fails with shares on /var or
> /shm/var... The only way I can get it to work is with 'wide links = Yes'
> parameter. In fact I cannot find any location that works with 'wide
> links = no'. Do you have shares on /var working with 'wide links = No'?

No.
wide links = yes used to be the default on Samba, but they changed it.  
That's why it's failing all the sudden.
It has to do with the symlinks we're using.
One thing you can try is pointing TMP to a different location before  
you start samba, so that there's no symlink being used (i.e. /shm/tmp  
). I did a lot of trial and error when I analyzed it first. Don't  
remember all the things I did.

I'm planning to not use many symlinks in the next major DL release,  
but rather use the "bind" feature of mount. This should help prevent  
problems like this.

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Re: [Devil-Linux-discuss] Samba wide links problems: canonicalize_connect_path failed

[Dominic R. <dl...@ed...>]

On 22/01/11 20:20, Heiko Zuerker wrote:
> Quoting Dominic Raferd<dl...@ed...>:
>> On 22/01/11 12:06, Heiko Zuerker wrote:
>>> Quoting Dominic Raferd<dl...@ed...>:
>>>
>>>> On 22/01/11 11:45, Heiko Zuerker wrote:
>>>>> Quoting Dominic Raferd<dl...@ed...>:
>>>>>> Thanks Heiko, but I do not have /var anywhere in my smb.conf file. I
>>>>>> only have paths that are subdirectories of /home.
>>>>> Okay.
>>>>>
>>>>> Do you have this line in the smb.conf?
>>>>>
>>>>> [IPC$]
>>>>> wide links = Yes
>>>>>
>>>> No, I have no reference to IPC at all. I think IPC is some internal
>>>> Samba thingy. I do have 'wide links = Yes' in all my shares (but IPC is
>>>> not among them) - I want to have wide links = No (the default - safe -
>>>> setting) but this prevents access.
>>> Add the above 2 lines to your smb.conf and things should work better.
>>> It's a hidden share which is being used for the communication.
>>> (Not sure about the details on it).
>> If I add lines:
>>
>> [IPC$]
>>       path = /shm/var/tmp
>>       wide links = Yes
>>
>> then the errors in log about IPC stop, which is good, thanks. Both of
>> these lines are needed. But if I have a share with wide links = No and I
>> try to connect to it I still see this in the log:
>>
>> [2011/01/22 14:27:18.361834,  0] smbd/service.c:988(make_connection_snum)
>>     canonicalize_connect_path failed for service exampleshare, path
>> /home/z-shares/exampleshare
> I don't understand why it fails on /home, the ones I used under /var
> were explained by the symlink.
>
And it not only fails on /home, it also fails with shares on /var or 
/shm/var... The only way I can get it to work is with 'wide links = Yes' 
parameter. In fact I cannot find any location that works with 'wide 
links = no'. Do you have shares on /var working with 'wide links = No'?

Re: [Devil-Linux-discuss] Samba wide links problems: canonicalize_connect_path failed

[Heiko Z. <he...@zu...>]

Quoting Dominic Raferd <dl...@ed...>:
> On 22/01/11 12:06, Heiko Zuerker wrote:
>> Quoting Dominic Raferd<dl...@ed...>:
>>
>>> On 22/01/11 11:45, Heiko Zuerker wrote:
>>>> Quoting Dominic Raferd<dl...@ed...>:
>>>>> Thanks Heiko, but I do not have /var anywhere in my smb.conf file. I
>>>>> only have paths that are subdirectories of /home.
>>>> Okay.
>>>>
>>>> Do you have this line in the smb.conf?
>>>>
>>>> [IPC$]
>>>> wide links = Yes
>>>>
>>> No, I have no reference to IPC at all. I think IPC is some internal
>>> Samba thingy. I do have 'wide links = Yes' in all my shares (but IPC is
>>> not among them) - I want to have wide links = No (the default - safe -
>>> setting) but this prevents access.
>> Add the above 2 lines to your smb.conf and things should work better.
>> It's a hidden share which is being used for the communication.
>> (Not sure about the details on it).
> If I add lines:
>
> [IPC$]
>      path = /shm/var/tmp
>      wide links = Yes
>
> then the errors in log about IPC stop, which is good, thanks. Both of
> these lines are needed. But if I have a share with wide links = No and I
> try to connect to it I still see this in the log:
>
> [2011/01/22 14:27:18.361834,  0] smbd/service.c:988(make_connection_snum)
>    canonicalize_connect_path failed for service exampleshare, path
> /home/z-shares/exampleshare

I don't understand why it fails on /home, the ones I used under /var  
were explained by the symlink.

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Re: [Devil-Linux-discuss] Samba wide links problems: canonicalize_connect_path failed

[Dominic R. <dl...@ed...>]

On 22/01/11 12:06, Heiko Zuerker wrote:
> Quoting Dominic Raferd<dl...@ed...>:
>
>> On 22/01/11 11:45, Heiko Zuerker wrote:
>>> Quoting Dominic Raferd<dl...@ed...>:
>>>> Thanks Heiko, but I do not have /var anywhere in my smb.conf file. I
>>>> only have paths that are subdirectories of /home.
>>> Okay.
>>>
>>> Do you have this line in the smb.conf?
>>>
>>> [IPC$]
>>> wide links = Yes
>>>
>> No, I have no reference to IPC at all. I think IPC is some internal
>> Samba thingy. I do have 'wide links = Yes' in all my shares (but IPC is
>> not among them) - I want to have wide links = No (the default - safe -
>> setting) but this prevents access.
> Add the above 2 lines to your smb.conf and things should work better.
> It's a hidden share which is being used for the communication.
> (Not sure about the details on it).
If I add lines:

[IPC$]
     path = /shm/var/tmp
     wide links = Yes

then the errors in log about IPC stop, which is good, thanks. Both of 
these lines are needed. But if I have a share with wide links = No and I 
try to connect to it I still see this in the log:

[2011/01/22 14:27:18.361834,  0] smbd/service.c:988(make_connection_snum)
   canonicalize_connect_path failed for service exampleshare, path 
/home/z-shares/exampleshare

Re: [Devil-Linux-discuss] Samba wide links problems: canonicalize_connect_path failed

[Heiko Z. <he...@zu...>]

Quoting Dominic Raferd <dl...@ed...>:

> On 22/01/11 11:45, Heiko Zuerker wrote:
>> Quoting Dominic Raferd<dl...@ed...>:
>>> Thanks Heiko, but I do not have /var anywhere in my smb.conf file. I
>>> only have paths that are subdirectories of /home.
>> Okay.
>>
>> Do you have this line in the smb.conf?
>>
>> [IPC$]
>> wide links = Yes
>>
> No, I have no reference to IPC at all. I think IPC is some internal
> Samba thingy. I do have 'wide links = Yes' in all my shares (but IPC is
> not among them) - I want to have wide links = No (the default - safe -
> setting) but this prevents access.

Add the above 2 lines to your smb.conf and things should work better.
It's a hidden share which is being used for the communication.
(Not sure about the details on it).

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Re: [Devil-Linux-discuss] Samba wide links problems: canonicalize_connect_path failed

[Dominic R. <dl...@ed...>]

On 22/01/11 11:45, Heiko Zuerker wrote:
> Quoting Dominic Raferd<dl...@ed...>:
>> Thanks Heiko, but I do not have /var anywhere in my smb.conf file. I
>> only have paths that are subdirectories of /home.
> Okay.
>
> Do you have this line in the smb.conf?
>
> [IPC$]
> wide links = Yes
>
No, I have no reference to IPC at all. I think IPC is some internal 
Samba thingy. I do have 'wide links = Yes' in all my shares (but IPC is 
not among them) - I want to have wide links = No (the default - safe - 
setting) but this prevents access.

Re: [Devil-Linux-discuss] Samba wide links problems: canonicalize_connect_path failed

[Heiko Z. <he...@zu...>]

Quoting Dominic Raferd <dl...@ed...>:
>
> Thanks Heiko, but I do not have /var anywhere in my smb.conf file. I
> only have paths that are subdirectories of /home.

Okay.

Do you have this line in the smb.conf?

[IPC$]
wide links = Yes

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Re: [Devil-Linux-discuss] Samba wide links problems: canonicalize_connect_path failed

[Dominic R. <dl...@ed...>]

Thanks Heiko, but I do not have /var anywhere in my smb.conf file. I 
only have paths that are subdirectories of /home.

Dominic

On 21/01/11 19:33, Heiko Zuerker wrote:
> I don't have much time, so this is going to be a brief answer.
> The issue is because we did symlink /var. You may get around some of
> the issues by specifying /shm/var in smb.conf as the path for the
> shares.
>
> Check the mailinglist archives, I think I posted a fix for a couple of
> the issues.
>
> Heiko
>
> Quoting Dominic Raferd<dl...@ed...>:
>
>> The Samba update (to 3.5.6 from 3.4.5) in DL 1.4.1 is presenting me with
>> some problems.
>>
>> The first issue is that I see a lot of messages in my log like this:
>>
>> smbd[21663]:   canonicalize_connect_path failed for service IPC$, path /tmp
>>
>> I wonder if this is because /tmp is a symlink in read-only file system
>> to /var/tmp rather than to the 'true' path which I think is
>> /shm/var/tmp? Is there any way for me to change this and see if it helps?
>>
>> The second issue is more serious but probably related in some way. I
>> have to use the setting 'wide links=yes' in my shares or else there is
>> no access to them. This is not a good setup because 'wide links' carries
>> some security risks and anyway I am not using any wide links. (The 'unix
>> extensions=yes/no' setting in [global] has no affect on this problem.)
>>
>> My samba paths are all inside /home with generous permissions so there
>> is no good reason IMO why Samba's canonicalize_connect_path should fail:
>> -----------
>> # ls /home -dl
>> drwxrwxrwx 8 root root 216 Jan  5 12:14 /home
>> # ls /home/z-shares -dl
>> drwxrwxrwx 9 root root 216 Dec 17 13:50 /home/z-shares
>> # ls /home/z-shares/* -dl
>> drwxrwxrwx 21 nobody  nogroup   872 Jan 21 04:22 /home/z-shares/exampleshare
>> # grep -A 6 "^\[exampleshare]" /etc/samba/smb.conf
>> [exampleshare]
>>           path = /home/z-shares/exampleshare
>>           valid users = myname_machine
>>           guest ok = No
>>           read only = No
>>           browseable = Yes
>>           wide links = No
>> -----------
>> With this setting 'wide links=No' (which is the default setting for
>> Samba 3.5), then attempting to connect to exampleshare fails, and log shows:
>> canonicalize_connect_path failed for service exampleshare, path
>> /home/z-shares/exampleshare
>>
>> I can't see any reason for this failure as the path looks fine and so do
>> the permissions. I should mention that I don't (and never have) run
>> winbindd (which normally runs on DL as a component of Samba) but I can't
>> see how this would affect anything.
>>
>> If I set 'widelinks = Yes', access is okay (but I still see error
>> messages relating to IPC$ in the log).
>>
>> [Delving deeper into Samba code than is probably wise, the function
>> which is returning an error is SMB_VFS_REALPATH. The actual call to this
>> function has two forms depending on whether a compile setting
>> REALPATH_TAKES_NULL is set or not. From what I can see this is not set
>> in DL's configuration. (No, it doesn't mean much to me either.)]
>>
>> All suggestions gratefully received.
>>
>> Googling, I don't see other Samba users having the same issue, so that
>> points me back towards DL configuration. Is anyone using Samba under DL
>> 1.4.1 or 1.4.2, or could someone running DL 1.4.1 or 1.4.2 test Samba to
>> see if they find the same problems?
>>
>> Dominic
>>
>> ------------------------------------------------------------------------------
>> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
>> Finally, a world-class log management solution at an even better price-free!
>> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
>> February 28th, so secure your free ArcSight Logger TODAY!
>> http://p.sf.net/sfu/arcsight-sfd2d
>> _______________________________________________
>> Devil-linux-discuss mailing list
>> Dev...@li...
>> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>>
>
>

Re: [Devil-Linux-discuss] Samba wide links problems: canonicalize_connect_path failed

[Heiko Z. <he...@zu...>]

I don't have much time, so this is going to be a brief answer.
The issue is because we did symlink /var. You may get around some of  
the issues by specifying /shm/var in smb.conf as the path for the  
shares.

Check the mailinglist archives, I think I posted a fix for a couple of  
the issues.

Heiko

Quoting Dominic Raferd <dl...@ed...>:

> The Samba update (to 3.5.6 from 3.4.5) in DL 1.4.1 is presenting me with
> some problems.
>
> The first issue is that I see a lot of messages in my log like this:
>
> smbd[21663]:   canonicalize_connect_path failed for service IPC$, path /tmp
>
> I wonder if this is because /tmp is a symlink in read-only file system
> to /var/tmp rather than to the 'true' path which I think is
> /shm/var/tmp? Is there any way for me to change this and see if it helps?
>
> The second issue is more serious but probably related in some way. I
> have to use the setting 'wide links=yes' in my shares or else there is
> no access to them. This is not a good setup because 'wide links' carries
> some security risks and anyway I am not using any wide links. (The 'unix
> extensions=yes/no' setting in [global] has no affect on this problem.)
>
> My samba paths are all inside /home with generous permissions so there
> is no good reason IMO why Samba's canonicalize_connect_path should fail:
> -----------
> # ls /home -dl
> drwxrwxrwx 8 root root 216 Jan  5 12:14 /home
> # ls /home/z-shares -dl
> drwxrwxrwx 9 root root 216 Dec 17 13:50 /home/z-shares
> # ls /home/z-shares/* -dl
> drwxrwxrwx 21 nobody  nogroup   872 Jan 21 04:22 /home/z-shares/exampleshare
> # grep -A 6 "^\[exampleshare]" /etc/samba/smb.conf
> [exampleshare]
>          path = /home/z-shares/exampleshare
>          valid users = myname_machine
>          guest ok = No
>          read only = No
>          browseable = Yes
>          wide links = No
> -----------
> With this setting 'wide links=No' (which is the default setting for
> Samba 3.5), then attempting to connect to exampleshare fails, and log shows:
> canonicalize_connect_path failed for service exampleshare, path
> /home/z-shares/exampleshare
>
> I can't see any reason for this failure as the path looks fine and so do
> the permissions. I should mention that I don't (and never have) run
> winbindd (which normally runs on DL as a component of Samba) but I can't
> see how this would affect anything.
>
> If I set 'widelinks = Yes', access is okay (but I still see error
> messages relating to IPC$ in the log).
>
> [Delving deeper into Samba code than is probably wise, the function
> which is returning an error is SMB_VFS_REALPATH. The actual call to this
> function has two forms depending on whether a compile setting
> REALPATH_TAKES_NULL is set or not. From what I can see this is not set
> in DL's configuration. (No, it doesn't mean much to me either.)]
>
> All suggestions gratefully received.
>
> Googling, I don't see other Samba users having the same issue, so that
> points me back towards DL configuration. Is anyone using Samba under DL
> 1.4.1 or 1.4.2, or could someone running DL 1.4.1 or 1.4.2 test Samba to
> see if they find the same problems?
>
> Dominic
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>



-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

[Devil-Linux-discuss] Samba wide links problems: canonicalize_connect_path failed

[Dominic R. <dl...@ed...>]

The Samba update (to 3.5.6 from 3.4.5) in DL 1.4.1 is presenting me with 
some problems.

The first issue is that I see a lot of messages in my log like this:

smbd[21663]:   canonicalize_connect_path failed for service IPC$, path /tmp

I wonder if this is because /tmp is a symlink in read-only file system 
to /var/tmp rather than to the 'true' path which I think is 
/shm/var/tmp? Is there any way for me to change this and see if it helps?

The second issue is more serious but probably related in some way. I 
have to use the setting 'wide links=yes' in my shares or else there is 
no access to them. This is not a good setup because 'wide links' carries 
some security risks and anyway I am not using any wide links. (The 'unix 
extensions=yes/no' setting in [global] has no affect on this problem.)

My samba paths are all inside /home with generous permissions so there 
is no good reason IMO why Samba's canonicalize_connect_path should fail:
-----------
# ls /home -dl
drwxrwxrwx 8 root root 216 Jan  5 12:14 /home
# ls /home/z-shares -dl
drwxrwxrwx 9 root root 216 Dec 17 13:50 /home/z-shares
# ls /home/z-shares/* -dl
drwxrwxrwx 21 nobody  nogroup   872 Jan 21 04:22 /home/z-shares/exampleshare
# grep -A 6 "^\[exampleshare]" /etc/samba/smb.conf
[exampleshare]
         path = /home/z-shares/exampleshare
         valid users = myname_machine
         guest ok = No
         read only = No
         browseable = Yes
         wide links = No
-----------
With this setting 'wide links=No' (which is the default setting for 
Samba 3.5), then attempting to connect to exampleshare fails, and log shows:
canonicalize_connect_path failed for service exampleshare, path 
/home/z-shares/exampleshare

I can't see any reason for this failure as the path looks fine and so do 
the permissions. I should mention that I don't (and never have) run 
winbindd (which normally runs on DL as a component of Samba) but I can't 
see how this would affect anything.

If I set 'widelinks = Yes', access is okay (but I still see error 
messages relating to IPC$ in the log).

[Delving deeper into Samba code than is probably wise, the function 
which is returning an error is SMB_VFS_REALPATH. The actual call to this 
function has two forms depending on whether a compile setting 
REALPATH_TAKES_NULL is set or not. From what I can see this is not set 
in DL's configuration. (No, it doesn't mean much to me either.)]

All suggestions gratefully received.

Googling, I don't see other Samba users having the same issue, so that 
points me back towards DL configuration. Is anyone using Samba under DL 
1.4.1 or 1.4.2, or could someone running DL 1.4.1 or 1.4.2 test Samba to 
see if they find the same problems?

Dominic

Re: [Devil-Linux-discuss] System-Crash with SMP

[Dietmar R. <die...@gm...>]

2011/1/20 Heiko Zuerker <he...@zu...>:
> Quoting xy zy <big...@fr...>:
>
> I tested it, and it's working. (1.4.2-i686)
> I'm waiting for new version. (updates shorewall)
>
>  I'm uploading the latest test build. It should be done about 30 minutes
> after this email was sent.
>

Thank you very much, everything works fine now!

Didi

Re: [Devil-Linux-discuss] System-Crash with SMP

[Heiko Z. <he...@zu...>]

Quoting xy zy <big...@fr...>: 

> I tested it, and it's working. (1.4.2-i686) 
>
> I'm waiting for new version. (updates shorewall)

 I'm uploading the latest test build. It should be done about 30 minutes after this email was sent.

-- 

Regards
  Heiko Zuerker
http://www.devil-linux.org

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Re: [Devil-Linux-discuss] System-Crash with SMP

[xy zy <big...@fr...>]

I tested it, and it's working. (1.4.2-i686) I'm waiting for new version. (updates shorewall) Great job! Regards, Boki 
>Did you try the version I uploaded to the FTP server in the testing directory?
>I removed all 3 Hungary download sites.
>Heiko
> 
>Hi,  >There was a bug in the build script.
>>The next compile will have the correct number of CPUs (16) and also 
>>the new shorewall.
>>
>>--
>>
>>Regards
>>  Heiko Zuerker
>>   http://www.devil-linux.org
> I agree with Dietmar and Joachim. I have the same problem.I tried 1.4.1.-i486, 1.4.1.-i686 version, and both of them restart after loading initial ramdisk without error screen.
> Other thing: On devil-linux.org under Downloads are 3 opportunity from Hungary but none of them is working. Thanks for Your great job! Best Regards, Boki 
> 
>--
>
>Regards
>  Heiko Zuerker
>http://www.devil-linux.org
>
>
>----------------------------------------------------------------
>This message was sent using IMP, the Internet Messaging Program.

Re: [Devil-Linux-discuss] System-Crash with SMP

[Heiko Z. <he...@zu...>]

Did you try the version I uploaded to the FTP server in the testing directory? 

I removed all 3 Hungary download sites. 

Heiko

Quoting xy zy <big...@fr...>: 

> Hi, 
>
>
> >There was a bug in the build script.
> >The next compile will have the correct number of CPUs (16) and also 
> >the new shorewall.
> >
> >--
> >
> >Regards
> >  Heiko Zuerker
> >   http://www.devil-linux.org
>
> I agree with Dietmar and Joachim. I have the same problem. 
> I tried 1.4.1.-i486, 1.4.1.-i686 version, and both of them restart after loading initial ramdisk without error screen.
>
>
> Other thing: 
>
> On devil-linux.org under Downloads are 3 opportunity from Hungary but none of them is working.  
>
> Thanks for Your great job! 
>
> Best Regards, 
>
> Boki

-- 

Regards
  Heiko Zuerker
http://www.devil-linux.org

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Re: [Devil-Linux-discuss] System-Crash with SMP

[xy zy <big...@fr...>]

Hi,  >There was a bug in the build script.
>The next compile will have the correct number of CPUs (16) and also 
>the new shorewall.
>
>--
>
>Regards
>  Heiko Zuerker
>   http://www.devil-linux.org
 I agree with Dietmar and Joachim. I have the same problem.I tried 1.4.1.-i486, 1.4.1.-i686 version, and both of them restart after loading initial ramdisk without error screen.
 Other thing: On devil-linux.org under Downloads are 3 opportunity from Hungary but none of them is working. Thanks for Your great job! Best Regards, Boki 

Re: [Devil-Linux-discuss] System-Crash with SMP

[Heiko Z. <he...@zu...>]

Quoting Heiko Zuerker <he...@zu...>:

> Quoting Dietmar Rieder <die...@gm...>:
>> I tested the new build now and it boots w/o problem. The only thing is
>> that there is still the limit of 4 CPUs so could that be raised to 16
>> for the next release?
>
> That should have been fixed....
> I'll look into it.

There was a bug in the build script.
The next compile will have the correct number of CPUs (16) and also  
the new shorewall.

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Re: [Devil-Linux-discuss] System-Crash with SMP

[Heiko Z. <he...@zu...>]

Quoting Dietmar Rieder <die...@gm...>:
> I tested the new build now and it boots w/o problem. The only thing is
> that there is still the limit of 4 CPUs so could that be raised to 16
> for the next release?

That should have been fixed....
I'll look into it.

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.