SEO

Hi,
I have a client who runs make_recovery each friday night. Last week he
encountered some errors but it looks like the backup still ran successfully.
Just need to know if these errors are of concern as I have not come across
these before:
"Warning message: There was a problem with the list of files/directories to
archive.
Input: /var/opt/ignite/recovery/2006-07-31,21:00/flist
The following line(s) had too few/incorrect entries:
Problem lines:
line: 29 u2/uda/HTG/MOD.F55/SR593.4A_ 100777 1077060389 17478 18
line: 39 u3/ARMIDALE/ARMIDALE/MOD.OLD/SR593.4A_ 100770 1081927777 17478 18
line: 31 spare/ABSMVP/MOD.OLD/SR593.4A_ 100660 1084520870 17478 18
line: 42 spare/TRAINING/ARMIDALE/MOD.OLD/SR593.4A_ 100660 1154303646 17478
18
line: 32 conv/ARM31MAR/MOD.OLD/SR593.4A_ 100660 1080732046 17478 18
line: 41 conv/ARMIDALE/ARMIDALE/MOD.OLD/SR593.4A_ 100770 1081927777 17478 18

NOTE: Could not read the /etc/resolv.conf file.
*Cleaning up old configuration file directories

07/31/06 21:36:18 EST make_recovery completed with warnings"

Many Thanks

Pedds : )

On Fri, 11 Aug 2006 09:21:30 +1000, connect wrote:
> Input: /var/opt/ignite/recovery/2006-07-31,21:00/flist The following
> line(s) had too few/incorrect entries: Problem lines:
> line: 29 u2/uda/HTG/MOD.F55/SR593.4A_ 100777 1077060389 17478 18 line: 39
> u3/ARMIDALE/ARMIDALE/MOD.OLD/SR593.4A_ 100770 1081927777 17478 18 line: 31
> spare/ABSMVP/MOD.OLD/SR593.4A_ 100660 1084520870 17478 18 line: 42
> spare/TRAINING/ARMIDALE/MOD.OLD/SR593.4A_ 100660 1154303646 17478 18
> line: 32 conv/ARM31MAR/MOD.OLD/SR593.4A_ 100660 1080732046 17478 18 line:
> 41 conv/ARMIDALE/ARMIDALE/MOD.OLD/SR593.4A_ 100770 1081927777 17478 18
>

When I've had these errors in the past it was because someone had produced
a file with strange characters in the name. In my case it was new-line
characters. This caused parsing errors of the make_recovery file index..

JohnK

Thank You John,
I'll have a look - and hopefully this resolves my issue.
Basically I was more worried if it meant the backups weren't performing
correctly.

Tahnks Again
Pedds : )
"JohnK" <johnk.dev.null@gmail.com> wrote in message
newsan.2006.08.12.08.32.14.996769@gmail.com...
> On Fri, 11 Aug 2006 09:21:30 +1000, connect wrote:
>> Input: /var/opt/ignite/recovery/2006-07-31,21:00/flist The following
>> line(s) had too few/incorrect entries: Problem lines:
>> line: 29 u2/uda/HTG/MOD.F55/SR593.4A_ 100777 1077060389 17478 18 line: 39
>> u3/ARMIDALE/ARMIDALE/MOD.OLD/SR593.4A_ 100770 1081927777 17478 18 line:
>> 31
>> spare/ABSMVP/MOD.OLD/SR593.4A_ 100660 1084520870 17478 18 line: 42
>> spare/TRAINING/ARMIDALE/MOD.OLD/SR593.4A_ 100660 1154303646 17478 18
>> line: 32 conv/ARM31MAR/MOD.OLD/SR593.4A_ 100660 1080732046 17478 18 line:
>> 41 conv/ARMIDALE/ARMIDALE/MOD.OLD/SR593.4A_ 100770 1081927777 17478 18
>>
>
> When I've had these errors in the past it was because someone had produced
> a file with strange characters in the name. In my case it was new-line
> characters. This caused parsing errors of the make_recovery file index..
>
> JohnK

Hi Guys,
Yes you were right JohnK. The files had underscores after the filename.
Thanks Again for that insight.

I have another question for you or anyone who can answer this the
/etc/resolv.conf file needs to be on the system correct?
Its just that the I can not find this file on the clients system where it
should be /etc.... Are there any drawbacks because of this?

Many Thanks
Pedds : )
"connect" <pamato@ultradata.com.au> wrote in message
news:ebop6p$ga8$1@news-01.bur.connect.com.au...
> Thank You John,
> I'll have a look - and hopefully this resolves my issue.
> Basically I was more worried if it meant the backups weren't performing
> correctly.
>
> Tahnks Again
> Pedds : )
> "JohnK" <johnk.dev.null@gmail.com> wrote in message
> newsan.2006.08.12.08.32.14.996769@gmail.com...
>> On Fri, 11 Aug 2006 09:21:30 +1000, connect wrote:
>>> Input: /var/opt/ignite/recovery/2006-07-31,21:00/flist The following
>>> line(s) had too few/incorrect entries: Problem lines:
>>> line: 29 u2/uda/HTG/MOD.F55/SR593.4A_ 100777 1077060389 17478 18 line:
>>> 39
>>> u3/ARMIDALE/ARMIDALE/MOD.OLD/SR593.4A_ 100770 1081927777 17478 18 line:
>>> 31
>>> spare/ABSMVP/MOD.OLD/SR593.4A_ 100660 1084520870 17478 18 line: 42
>>> spare/TRAINING/ARMIDALE/MOD.OLD/SR593.4A_ 100660 1154303646 17478 18
>>> line: 32 conv/ARM31MAR/MOD.OLD/SR593.4A_ 100660 1080732046 17478 18
>>> line:
>>> 41 conv/ARMIDALE/ARMIDALE/MOD.OLD/SR593.4A_ 100770 1081927777 17478 18
>>>
>>
>> When I've had these errors in the past it was because someone had
>> produced
>> a file with strange characters in the name. In my case it was new-line
>> characters. This caused parsing errors of the make_recovery file index..
>>
>> JohnK
>
>

JohnK <johnk.dev.null@gmail.com> writes:

> On Fri, 11 Aug 2006 09:21:30 +1000, connect wrote:
> > Input: /var/opt/ignite/recovery/2006-07-31,21:00/flist The following
> > line(s) had too few/incorrect entries: Problem lines:
> > line: 29 u2/uda/HTG/MOD.F55/SR593.4A_ 100777 1077060389 17478 18 line: 39
> > u3/ARMIDALE/ARMIDALE/MOD.OLD/SR593.4A_ 100770 1081927777 17478 18 line: 31
> > spare/ABSMVP/MOD.OLD/SR593.4A_ 100660 1084520870 17478 18 line: 42
> > spare/TRAINING/ARMIDALE/MOD.OLD/SR593.4A_ 100660 1154303646 17478 18
> > line: 32 conv/ARM31MAR/MOD.OLD/SR593.4A_ 100660 1080732046 17478 18 line:
> > 41 conv/ARMIDALE/ARMIDALE/MOD.OLD/SR593.4A_ 100770 1081927777 17478 18
> >
>
> When I've had these errors in the past it was because someone had produced
> a file with strange characters in the name. In my case it was new-line
> characters. This caused parsing errors of the make_recovery file index..

As Ignite-UX writes that file, it should be able to read what it
wrote. Otherwise it should complain _before_ adding such names to the file.

MHO.

Ulrich