astlinux-devel Mailing List for AstLinux (Page 4)

On Apr 7, 2009, at 5:02 PM, Lonnie Abelbeck wrote:

> We just ran into a problem when PHP restarts the arno-iptables-
> firewall, where superfluous stdout error messages occur...
>
> "job-working-directory: error retrieving current directory: getcwd:
> cannot access parent directories: Success'
>
> I have also seen in the OpenVPN logs...
>
> "shell-init: error retrieving current directory: getcwd: cannot access
> parent directories: Inappropriate ioctl for device"
>
> Is there a kernel configuration option to turn off these problem
> messages?
>
> Lonnie


Replying to myself,

Problem solved on my end. In PHP...

1) @system('/usr/sbin/arno-iptables-firewall restart', $status);

Has all the spurious "job-working-directory: error retrieving current  
directory: getcwd:
cannot access parent directories: Success', which messes-up Arno's  
script.

2) @system('cd /root;/usr/sbin/arno-iptables-firewall restart',  
$status);

works perfectly and clean, and Arno's script runs perfectly.

Not sure why the 'cd' is required, but it solves the problem.

Lonnie

We just ran into a problem when PHP restarts the arno-iptables- 
firewall, where superfluous stdout error messages occur...

"job-working-directory: error retrieving current directory: getcwd:  
cannot access parent directories: Success'

I have also seen in the OpenVPN logs...

"shell-init: error retrieving current directory: getcwd: cannot access  
parent directories: Inappropriate ioctl for device"

Is there a kernel configuration option to turn off these problem  
messages?

Lonnie

On Apr 7, 2009, at 12:57 AM, Philip A. Prindeville wrote:

> dha...@us... wrote:
>> Revision: 2604
>>          http://astlinux.svn.sourceforge.net/astlinux/?rev=2604&view=rev
>> Author:   dhartman
>> Date:     2009-04-06 22:49:00 +0000 (Mon, 06 Apr 2009)
>>
>> Log Message:
>> -----------
>> merge upgrade-run-image change from trunk to make sure there is  
>> enough space on the disk
>>
>> Modified Paths:
>> --------------
>>    branches/0.6/target/generic/target_skeleton/usr/sbin/upgrade-run- 
>> image
>>
>> Modified: branches/0.6/target/generic/target_skeleton/usr/sbin/ 
>> upgrade-run-image
>> ===================================================================
>> --- branches/0.6/target/generic/target_skeleton/usr/sbin/upgrade- 
>> run-image	2009-04-06 22:19:34 UTC (rev 2603)
>> +++ branches/0.6/target/generic/target_skeleton/usr/sbin/upgrade- 
>> run-image	2009-04-06 22:49:00 UTC (rev 2604)
>> @@ -165,6 +165,7 @@
>>       rm -f $BASE/os/Xver
>>     fi
>>     tar -xzf /tmp/up/$VER.tar.gz -C $BASE/tmp/
>> +    TAR_ARCHIVE_RTN=$?
>>     sync
>>   else
>>     unmount_tmpfs_up
>> @@ -176,7 +177,7 @@
>>
>>   cd $BASE/tmp/$VER
>>
>> -  if sha1sum -cs $VER.run.sha1; then
>> +  if [ $TAR_ARCHIVE_RTN -eq 0 ] && sha1sum -cs $VER.run.sha1; then
>>     mv $BASE/tmp/$VER/* $BASE/os/
>>     echo "$OVER" > $BASE/os/Xver
>>     echo "$VER" > $BASE/os/ver
>> @@ -185,7 +186,11 @@
>>     unmount_tmpfs_up
>>     rm -r $BASE/tmp/
>>     unmount_oldroot_cdrom
>> -    echo "Firmware verification failed."
>> +    if [ $TAR_ARCHIVE_RTN -ne 0 ]; then
>> +      echo "Not enough free space for new firmware on the RUNNIX  
>> partition."
>> +    else
>> +      echo "Firmware verification failed."
>> +    fi
>>     exit $RED
>>   fi
>>
>>
>>
>
> You're making a small leap here...  tar can fail to unpack for any
> number of reasons, not just lack of space.  I'd pay attention to  
> whether
> it returns distinct exit codes or not (and even then, the BusyBox tar
> might behave differently from Gnu tar, etc)...  If tar fails, just say
> it failed.  Don't necessarily assume it was a space problem:  it would
> be a permissions problem, a corrupt tar ball, problems looking up user
> names or uids inside the tar ball, etc...
>
> -Philip

Philip,

This is a good addition, since tar's success is now required for a  
successful upgrade.

Since Darrick creates and controls the tar archives in question, I'm  
confident a tar error in this context is an out-of-space error.

BTW, the return code from tar with an out-of-space error is "1",  
pretty generic.

Lonnie

dha...@us... wrote:
> Revision: 2604
>           http://astlinux.svn.sourceforge.net/astlinux/?rev=2604&view=rev
> Author:   dhartman
> Date:     2009-04-06 22:49:00 +0000 (Mon, 06 Apr 2009)
>
> Log Message:
> -----------
> merge upgrade-run-image change from trunk to make sure there is enough space on the disk
>
> Modified Paths:
> --------------
>     branches/0.6/target/generic/target_skeleton/usr/sbin/upgrade-run-image
>
> Modified: branches/0.6/target/generic/target_skeleton/usr/sbin/upgrade-run-image
> ===================================================================
> --- branches/0.6/target/generic/target_skeleton/usr/sbin/upgrade-run-image	2009-04-06 22:19:34 UTC (rev 2603)
> +++ branches/0.6/target/generic/target_skeleton/usr/sbin/upgrade-run-image	2009-04-06 22:49:00 UTC (rev 2604)
> @@ -165,6 +165,7 @@
>        rm -f $BASE/os/Xver
>      fi
>      tar -xzf /tmp/up/$VER.tar.gz -C $BASE/tmp/
> +    TAR_ARCHIVE_RTN=$?
>      sync
>    else
>      unmount_tmpfs_up
> @@ -176,7 +177,7 @@
>  
>    cd $BASE/tmp/$VER
>  
> -  if sha1sum -cs $VER.run.sha1; then
> +  if [ $TAR_ARCHIVE_RTN -eq 0 ] && sha1sum -cs $VER.run.sha1; then
>      mv $BASE/tmp/$VER/* $BASE/os/
>      echo "$OVER" > $BASE/os/Xver
>      echo "$VER" > $BASE/os/ver
> @@ -185,7 +186,11 @@
>      unmount_tmpfs_up
>      rm -r $BASE/tmp/
>      unmount_oldroot_cdrom
> -    echo "Firmware verification failed."
> +    if [ $TAR_ARCHIVE_RTN -ne 0 ]; then
> +      echo "Not enough free space for new firmware on the RUNNIX partition."
> +    else
> +      echo "Firmware verification failed."
> +    fi
>      exit $RED
>    fi
>    
>
>   

You're making a small leap here...  tar can fail to unpack for any
number of reasons, not just lack of space.  I'd pay attention to whether
it returns distinct exit codes or not (and even then, the BusyBox tar
might behave differently from Gnu tar, etc)...  If tar fails, just say
it failed.  Don't necessarily assume it was a space problem:  it would
be a permissions problem, a corrupt tar ball, problems looking up user
names or uids inside the tar ball, etc...

-Philip

On Apr 6, 2009, at 2:29 PM, Philip Prindeville wrote:

> Lonnie Abelbeck wrote:
>> On Apr 4, 2009, at 6:05 PM, Darrick Hartman wrote:
>>
>>
>>> Lonnie Abelbeck wrote:
>>>
>>>> I'm considering making the current web interface version 1.4.0X the
>>>> last that works for the 0.6 branch. (Archived of course)
>>>>
>>>> I would then make the web interface 1.5.XX only work with the  
>>>> pre-0.7
>>>> branch and beyond.
>>>>
>>>> Currently, version 1.4.05 works on AstLinux 0.4.3 through pre-0.7.
>>>> It
>>>> would be nice to be able to simplify the logic, such as assuming  
>>>> Arno
>>>> 1.9 firewall.
>>>>
>>>> This should have no effect to anyone using the standard /stat/var/
>>>> www/
>>>> web interface.
>>>>
>>>> If this proposed change causes any concern, let me know.
>>>>
>>> Works for me.  I would still favor including your web interface in  
>>> the
>>> svn tree for the Astlinux project, but will respect your decision if
>>> you
>>> want to keep it as a separate entity.
>>>
>>> Darrick
>>>
>>
>> As long as the web interface is being actively developed, I prefer it
>> not to be directly in the SVN.
>>
>> Real time testing would be hard to give-up.
>>
>> Lonnie
>>
>
> Not sure I get what you mean...  I do all my testing (kernel, IPSec,
> scripts, FW, etc.) in a trunk check-out (or several, as the case may
> be), and then just check things back in when I'm happy with them.
>
> This wouldn't work for you?
>
> -Philip

I actually edit PHP/XHTML on a net5501, where I can make changes and  
view the output via a browser in a matter of seconds.  There is no  
better way to tweak layouts.

Lonnie

Lonnie Abelbeck wrote:
> On Apr 4, 2009, at 6:05 PM, Darrick Hartman wrote:
>
>   
>> Lonnie Abelbeck wrote:
>>     
>>> I'm considering making the current web interface version 1.4.0X the
>>> last that works for the 0.6 branch. (Archived of course)
>>>
>>> I would then make the web interface 1.5.XX only work with the pre-0.7
>>> branch and beyond.
>>>
>>> Currently, version 1.4.05 works on AstLinux 0.4.3 through pre-0.7.   
>>> It
>>> would be nice to be able to simplify the logic, such as assuming Arno
>>> 1.9 firewall.
>>>
>>> This should have no effect to anyone using the standard /stat/var/ 
>>> www/
>>> web interface.
>>>
>>> If this proposed change causes any concern, let me know.
>>>       
>> Works for me.  I would still favor including your web interface in the
>> svn tree for the Astlinux project, but will respect your decision if  
>> you
>> want to keep it as a separate entity.
>>
>> Darrick
>>     
>
> As long as the web interface is being actively developed, I prefer it  
> not to be directly in the SVN.
>
> Real time testing would be hard to give-up.
>
> Lonnie
>   

Not sure I get what you mean...  I do all my testing (kernel, IPSec, 
scripts, FW, etc.) in a trunk check-out (or several, as the case may 
be), and then just check things back in when I'm happy with them.

This wouldn't work for you?

-Philip

On Apr 4, 2009, at 6:05 PM, Darrick Hartman wrote:

> Lonnie Abelbeck wrote:
>> I'm considering making the current web interface version 1.4.0X the
>> last that works for the 0.6 branch. (Archived of course)
>>
>> I would then make the web interface 1.5.XX only work with the pre-0.7
>> branch and beyond.
>>
>> Currently, version 1.4.05 works on AstLinux 0.4.3 through pre-0.7.   
>> It
>> would be nice to be able to simplify the logic, such as assuming Arno
>> 1.9 firewall.
>>
>> This should have no effect to anyone using the standard /stat/var/ 
>> www/
>> web interface.
>>
>> If this proposed change causes any concern, let me know.
>
> Works for me.  I would still favor including your web interface in the
> svn tree for the Astlinux project, but will respect your decision if  
> you
> want to keep it as a separate entity.
>
> Darrick

As long as the web interface is being actively developed, I prefer it  
not to be directly in the SVN.

Real time testing would be hard to give-up.

Lonnie

Lonnie Abelbeck wrote:
> I'm considering making the current web interface version 1.4.0X the  
> last that works for the 0.6 branch. (Archived of course)
> 
> I would then make the web interface 1.5.XX only work with the pre-0.7  
> branch and beyond.
> 
> Currently, version 1.4.05 works on AstLinux 0.4.3 through pre-0.7.  It  
> would be nice to be able to simplify the logic, such as assuming Arno  
> 1.9 firewall.
> 
> This should have no effect to anyone using the standard /stat/var/www/  
> web interface.
> 
> If this proposed change causes any concern, let me know.

Works for me.  I would still favor including your web interface in the 
svn tree for the Astlinux project, but will respect your decision if you 
want to keep it as a separate entity.

Darrick

I'm considering making the current web interface version 1.4.0X the  
last that works for the 0.6 branch. (Archived of course)

I would then make the web interface 1.5.XX only work with the pre-0.7  
branch and beyond.

Currently, version 1.4.05 works on AstLinux 0.4.3 through pre-0.7.  It  
would be nice to be able to simplify the logic, such as assuming Arno  
1.9 firewall.

This should have no effect to anyone using the standard /stat/var/www/  
web interface.

If this proposed change causes any concern, let me know.

Lonnie

David,


   Have you tested your 2592 build? Did it boot properly?

                - Justin

David Kerr wrote:
> Clean build (svn 2592) working again.  Thanks.
>
> On Tue, Mar 31, 2009 at 9:52 PM, David Kerr <Da...@ke... 
> <mailto:Da...@ke...>> wrote:
>
>     thanks, I've deleted the arno download files. Next time build I'll
>     pick up the changes.
>
>     David 
>
>
>     On Tue, Mar 31, 2009 at 8:02 PM, Philip Prindeville
>     <phi...@re...
>     <mailto:phi...@re...>> wrote:
>
>         Lonnie Abelbeck wrote:
>         > On Mar 31, 2009, at 6:01 PM, Philip Prindeville wrote:
>         >
>         >
>         >> Darrick Hartman wrote:
>         >>
>         >>> David Kerr wrote:
>         >>>
>         >>>
>         >>>> I just updated my trunk source (from 2577 to 2587 to get
>         the DST
>         >>>> fix)
>         >>>> and tried a clean build (erased build_i586) and got the
>         following...
>         >>>>
>         >>>> Applying arnofw-tracing.patch using plaintext:
>         >>>> patching file share/arno-iptables-firewall/environment
>         >>>> Hunk #1 succeeded at 115 (offset 32 lines).
>         >>>> Hunk #2 FAILED at 170.
>         >>>> 1 out of 2 hunks FAILED -- saving rejects to file
>         >>>> share/arno-iptables-firewall/environment.rej
>         >>>> Patch failed!  Please fix arnofw-tracing.patch!
>         >>>> make: ***
>         >>>> [/home/david/astlinux-trunk/build_i586/arno-iptables-
>         >>>> firewall_1.9.0c/.patched]
>         >>>> Error 1
>         >>>>
>         >>>> What's up?
>         >>>>
>         >>>>
>         >>> David,
>         >>>
>         >>> Philip will be fixing that patch, but for now, you can
>         manually
>         >>> delete
>         >>> the patch locally.  He's adding a new feature that he
>         hopes will
>         >>> eventually be part of Arno's fw, but trunk also right now is
>         >>> pulling a
>         >>> nightly build rather than a released version.  That's why
>         the patch
>         >>> stopped working.
>         >>>
>         >>> Darrick
>         >>>
>         >>>
>         >> Resolved last night.... at least until the next time Arno
>         breaks
>         >> it.  :-)
>         >>
>         >> I sent him a copy of my patch.  Haven't heard back.
>         >>
>         >> -Philip
>         >>
>         >
>         > Thanks Philip.
>         >
>         > David, be sure to do a...
>         >
>         > $ rm dl/arno-iptables-firewall_1.9_nightly.tar.gz
>         >
>         > if it exists, to get the latest arno nightly.
>         >
>         > Lonnie
>         >
>
>         Or:
>
>         $ rm dl/arno-iptables-firewall_1.9_nightly.tar.gz*
>
>         to clobber the .sha1 file as well.
>
>         -Philip
>
>
>
>         ------------------------------------------------------------------------------
>         _______________________________________________
>         Astlinux-devel mailing list
>         Ast...@li...
>         <mailto:Ast...@li...>
>         https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>
>         Donations to support AstLinux are graciously accepted via
>         PayPal to pa...@kr... <mailto:pa...@kr...>.
>
>
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Clean build (svn 2592) working again.  Thanks.

On Tue, Mar 31, 2009 at 9:52 PM, David Kerr <Da...@ke...> wrote:

> thanks, I've deleted the arno download files. Next time build I'll pick up
> the changes.
> David
>
>
> On Tue, Mar 31, 2009 at 8:02 PM, Philip Prindeville <
> phi...@re...> wrote:
>
>> Lonnie Abelbeck wrote:
>> > On Mar 31, 2009, at 6:01 PM, Philip Prindeville wrote:
>> >
>> >
>> >> Darrick Hartman wrote:
>> >>
>> >>> David Kerr wrote:
>> >>>
>> >>>
>> >>>> I just updated my trunk source (from 2577 to 2587 to get the DST
>> >>>> fix)
>> >>>> and tried a clean build (erased build_i586) and got the following...
>> >>>>
>> >>>> Applying arnofw-tracing.patch using plaintext:
>> >>>> patching file share/arno-iptables-firewall/environment
>> >>>> Hunk #1 succeeded at 115 (offset 32 lines).
>> >>>> Hunk #2 FAILED at 170.
>> >>>> 1 out of 2 hunks FAILED -- saving rejects to file
>> >>>> share/arno-iptables-firewall/environment.rej
>> >>>> Patch failed!  Please fix arnofw-tracing.patch!
>> >>>> make: ***
>> >>>> [/home/david/astlinux-trunk/build_i586/arno-iptables-
>> >>>> firewall_1.9.0c/.patched]
>> >>>> Error 1
>> >>>>
>> >>>> What's up?
>> >>>>
>> >>>>
>> >>> David,
>> >>>
>> >>> Philip will be fixing that patch, but for now, you can manually
>> >>> delete
>> >>> the patch locally.  He's adding a new feature that he hopes will
>> >>> eventually be part of Arno's fw, but trunk also right now is
>> >>> pulling a
>> >>> nightly build rather than a released version.  That's why the patch
>> >>> stopped working.
>> >>>
>> >>> Darrick
>> >>>
>> >>>
>> >> Resolved last night.... at least until the next time Arno breaks
>> >> it.  :-)
>> >>
>> >> I sent him a copy of my patch.  Haven't heard back.
>> >>
>> >> -Philip
>> >>
>> >
>> > Thanks Philip.
>> >
>> > David, be sure to do a...
>> >
>> > $ rm dl/arno-iptables-firewall_1.9_nightly.tar.gz
>> >
>> > if it exists, to get the latest arno nightly.
>> >
>> > Lonnie
>> >
>>
>> Or:
>>
>> $ rm dl/arno-iptables-firewall_1.9_nightly.tar.gz*
>>
>> to clobber the .sha1 file as well.
>>
>> -Philip
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Astlinux-devel mailing list
>> Ast...@li...
>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>>
>> Donations to support AstLinux are graciously accepted via PayPal to
>> pa...@kr....
>>
>
>

thanks, I've deleted the arno download files. Next time build I'll pick up
the changes.
David

On Tue, Mar 31, 2009 at 8:02 PM, Philip Prindeville <
phi...@re...> wrote:

> Lonnie Abelbeck wrote:
> > On Mar 31, 2009, at 6:01 PM, Philip Prindeville wrote:
> >
> >
> >> Darrick Hartman wrote:
> >>
> >>> David Kerr wrote:
> >>>
> >>>
> >>>> I just updated my trunk source (from 2577 to 2587 to get the DST
> >>>> fix)
> >>>> and tried a clean build (erased build_i586) and got the following...
> >>>>
> >>>> Applying arnofw-tracing.patch using plaintext:
> >>>> patching file share/arno-iptables-firewall/environment
> >>>> Hunk #1 succeeded at 115 (offset 32 lines).
> >>>> Hunk #2 FAILED at 170.
> >>>> 1 out of 2 hunks FAILED -- saving rejects to file
> >>>> share/arno-iptables-firewall/environment.rej
> >>>> Patch failed!  Please fix arnofw-tracing.patch!
> >>>> make: ***
> >>>> [/home/david/astlinux-trunk/build_i586/arno-iptables-
> >>>> firewall_1.9.0c/.patched]
> >>>> Error 1
> >>>>
> >>>> What's up?
> >>>>
> >>>>
> >>> David,
> >>>
> >>> Philip will be fixing that patch, but for now, you can manually
> >>> delete
> >>> the patch locally.  He's adding a new feature that he hopes will
> >>> eventually be part of Arno's fw, but trunk also right now is
> >>> pulling a
> >>> nightly build rather than a released version.  That's why the patch
> >>> stopped working.
> >>>
> >>> Darrick
> >>>
> >>>
> >> Resolved last night.... at least until the next time Arno breaks
> >> it.  :-)
> >>
> >> I sent him a copy of my patch.  Haven't heard back.
> >>
> >> -Philip
> >>
> >
> > Thanks Philip.
> >
> > David, be sure to do a...
> >
> > $ rm dl/arno-iptables-firewall_1.9_nightly.tar.gz
> >
> > if it exists, to get the latest arno nightly.
> >
> > Lonnie
> >
>
> Or:
>
> $ rm dl/arno-iptables-firewall_1.9_nightly.tar.gz*
>
> to clobber the .sha1 file as well.
>
> -Philip
>
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>
> Donations to support AstLinux are graciously accepted via PayPal to
> pa...@kr....
>

Lonnie Abelbeck wrote:
> On Mar 31, 2009, at 6:01 PM, Philip Prindeville wrote:
>
>   
>> Darrick Hartman wrote:
>>     
>>> David Kerr wrote:
>>>
>>>       
>>>> I just updated my trunk source (from 2577 to 2587 to get the DST  
>>>> fix)
>>>> and tried a clean build (erased build_i586) and got the following...
>>>>
>>>> Applying arnofw-tracing.patch using plaintext:
>>>> patching file share/arno-iptables-firewall/environment
>>>> Hunk #1 succeeded at 115 (offset 32 lines).
>>>> Hunk #2 FAILED at 170.
>>>> 1 out of 2 hunks FAILED -- saving rejects to file
>>>> share/arno-iptables-firewall/environment.rej
>>>> Patch failed!  Please fix arnofw-tracing.patch!
>>>> make: ***
>>>> [/home/david/astlinux-trunk/build_i586/arno-iptables- 
>>>> firewall_1.9.0c/.patched]
>>>> Error 1
>>>>
>>>> What's up?
>>>>
>>>>         
>>> David,
>>>
>>> Philip will be fixing that patch, but for now, you can manually  
>>> delete
>>> the patch locally.  He's adding a new feature that he hopes will
>>> eventually be part of Arno's fw, but trunk also right now is  
>>> pulling a
>>> nightly build rather than a released version.  That's why the patch
>>> stopped working.
>>>
>>> Darrick
>>>
>>>       
>> Resolved last night.... at least until the next time Arno breaks  
>> it.  :-)
>>
>> I sent him a copy of my patch.  Haven't heard back.
>>
>> -Philip
>>     
>
> Thanks Philip.
>
> David, be sure to do a...
>
> $ rm dl/arno-iptables-firewall_1.9_nightly.tar.gz
>
> if it exists, to get the latest arno nightly.
>
> Lonnie
>   

Or:

$ rm dl/arno-iptables-firewall_1.9_nightly.tar.gz*

to clobber the .sha1 file as well.

-Philip