Re: incompatibilities with newer Postgresql

2023-12-24 Thread Trever L. Adams

I am assuming you mean something like:

CREATE FUNCTION pg_stop_backup ( ) RETURNS TABLE ( lsn pg_lsn, labelfile 
text, spcmapfile text )

   AS 'pg_backup_stop'
   LANGUAGE internal
   STRICT;

CREATE FUNCTION pg_start_backup(label text) RETURNS pg_lsn
   AS 'pg_backup_start'
   LANGUAGE internal
   STRICT;


On 12/21/23 10:07, Ingo Schaefer wrote:

Hello Trever,

you may define aliases for this functions with the "old" name like 
described here:

https://www.postgresql.org/docs/current/xfunc-internal.html

HTH,
Ingo
Am 21. Dez. 2023, um 15:11, "Trever L. Adams" 
 schrieb:


So, I am not sure which version started this problem with backing up
PostgreSQL.

| psql stderr: ERROR:  function pg_start_backup(unknown) does not exist
| psql stderr: LINE 1: SELECT pg_start_backup('amanda-1703142252')
| psql stderr:^
| psql stderr: HINT:  No function matches the given name and argument 
types. You might need to add explicit type casts.
??! Failed to call pg_start_backup

I believe the only change needs to be pg_backup_start instead of
pg_start_backup. The same change in order for pg_backup_stop. See table
9.92 athttps://www.postgresql.org/docs/current/functions-admin.html



incompatibilities with newer Postgresql

2023-12-21 Thread Trever L. Adams
So, I am not sure which version started this problem with backing up 
PostgreSQL.


  | psql stderr: ERROR:  function pg_start_backup(unknown) does not exist
  | psql stderr: LINE 1: SELECT pg_start_backup('amanda-1703142252')
  | psql stderr:^
  | psql stderr: HINT:  No function matches the given name and argument types. 
You might need to add explicit type casts.
  ??! Failed to call pg_start_backup

I believe the only change needs to be pg_backup_start instead of 
pg_start_backup. The same change in order for pg_backup_stop. See table 
9.92 at https://www.postgresql.org/docs/current/functions-admin.html




Re: incompatibilities with newer Postgresql

2023-12-21 Thread Trever L. Adams

On 12/21/23 07:08, Trever L. Adams wrote:
So, I am not sure which version started this problem with backing up 
PostgreSQL.


  | psql stderr: ERROR:  function pg_start_backup(unknown) does not exist
  | psql stderr: LINE 1: SELECT pg_start_backup('amanda-1703142252')
  | psql stderr:    ^
  | psql stderr: HINT:  No function matches the given name and 
argument types. You might need to add explicit type casts.

  ??! Failed to call pg_start_backup

I believe the only change needs to be pg_backup_start instead of 
pg_start_backup. The same change in order for pg_backup_stop. See 
table 9.92 at 
https://www.postgresql.org/docs/current/functions-admin.html



I am sorry, that is table 9.91.



amrecover failing

2014-07-19 Thread Trever L. Adams
Hello everyone,

So, I am not quite sure what is going on. When I try to do an amrecover,
I get the following:

Load tape normal149 now
Continue [?/Y/n/s/d]? Y
Got no header and data from server, check in amidxtaped.*.debug and
amandad.*.debug files on server

The logs hold such things as:

Sat Jul 19 05:45:39 2014: thd-0x1a16a00: amidxtaped: warning: Can't exec
-eo: No such file or directory at
/usr/lib64/perl5/vendor_perl/Amanda/Process.pm line 176.

Sat Jul 19 05:45:39 2014: thd-0x1a16a00: amidxtaped: critical (fatal): 
-eo pid,ppid,command: No such file or directory at
/usr/lib64/perl5/vendor_perl/Amanda/Process.pm line 176.

amidxtaped:  -eo pid,ppid,command: No such file or directory at
/usr/lib64/perl5/vendor_perl/Amanda/Process.pm line 176.

/lib64/libamanda-3.3.3.so(+0x2b727)[0x7f3e7d9d0727]
/lib64/libglib-2.0.so.0(g_logv+0x209)[0x7f3e7d6c9429]
/lib64/libglib-2.0.so.0(g_log+0x8f)[0x7f3e7d6c963f]
/usr/lib64/perl5/vendor_perl/auto/Amanda/MainLoop/libMainLoop.so(+0x4925)[0x7f3e7c5ad925]
/lib64/libglib-2.0.so.0(+0x3f89449e43)[0x7f3e7d6c2e43]
/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x166)[0x7f3e7d6c22a6]
/lib64/libglib-2.0.so.0(+0x3f89449628)[0x7f3e7d6c2628]
/lib64/libglib-2.0.so.0(g_main_loop_run+0x6a)[0x7f3e7d6c2a3a]
/usr/lib64/perl5/vendor_perl/auto/Amanda/MainLoop/libMainLoop.so(_wrap_run_c+0x50)[0x7f3e7c5adca0]
/lib64/libperl.so.5.18(Perl_pp_entersub+0x5c6)[0x3008ec33e6]
/lib64/libperl.so.5.18(Perl_runops_standard+0x2e)[0x3008ebb81e]
/lib64/libperl.so.5.18(perl_run+0x300)[0x3008e52d40]
/usr/bin/perl[0x400d29]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x3f86c21d65]
/usr/bin/perl[0x400d61]


This is also not 100% consistent. I got it to do a restore once. Doing
the same steps with the same disk and date will not restore, it is all
the above.

Any ideas?

Thank you,
Trever




signature.asc
Description: OpenPGP digital signature


Re: amrecover failing

2014-07-19 Thread Trever L. Adams
On 07/19/2014 01:13 PM, John Hein wrote:
 Trever L. Adams wrote at 05:49 -0600 on Jul 19, 2014:
   Hello everyone,
  
   So, I am not quite sure what is going on. When I try to do an amrecover,
   I get the following:
  
   Load tape normal149 now
   Continue [?/Y/n/s/d]? Y
   Got no header and data from server, check in amidxtaped.*.debug and
   amandad.*.debug files on server
  
   The logs hold such things as:
  
   Sat Jul 19 05:45:39 2014: thd-0x1a16a00: amidxtaped: warning: Can't exec
   -eo: No such file or directory at
   /usr/lib64/perl5/vendor_perl/Amanda/Process.pm line 176.
  
   Sat Jul 19 05:45:39 2014: thd-0x1a16a00: amidxtaped: critical (fatal):
   -eo pid,ppid,command: No such file or directory at
   /usr/lib64/perl5/vendor_perl/Amanda/Process.pm line 176.
  
   amidxtaped:  -eo pid,ppid,command: No such file or directory at
   /usr/lib64/perl5/vendor_perl/Amanda/Process.pm line 176.
  
   /lib64/libamanda-3.3.3.so(+0x2b727)[0x7f3e7d9d0727]
   /lib64/libglib-2.0.so.0(g_logv+0x209)[0x7f3e7d6c9429]
   /lib64/libglib-2.0.so.0(g_log+0x8f)[0x7f3e7d6c963f]
   
 /usr/lib64/perl5/vendor_perl/auto/Amanda/MainLoop/libMainLoop.so(+0x4925)[0x7f3e7c5ad925]
   /lib64/libglib-2.0.so.0(+0x3f89449e43)[0x7f3e7d6c2e43]
   /lib64/libglib-2.0.so.0(g_main_context_dispatch+0x166)[0x7f3e7d6c22a6]
   /lib64/libglib-2.0.so.0(+0x3f89449628)[0x7f3e7d6c2628]
   /lib64/libglib-2.0.so.0(g_main_loop_run+0x6a)[0x7f3e7d6c2a3a]
   
 /usr/lib64/perl5/vendor_perl/auto/Amanda/MainLoop/libMainLoop.so(_wrap_run_c+0x50)[0x7f3e7c5adca0]
   /lib64/libperl.so.5.18(Perl_pp_entersub+0x5c6)[0x3008ec33e6]
   /lib64/libperl.so.5.18(Perl_runops_standard+0x2e)[0x3008ebb81e]
   /lib64/libperl.so.5.18(perl_run+0x300)[0x3008e52d40]
   /usr/bin/perl[0x400d29]
   /lib64/libc.so.6(__libc_start_main+0xf5)[0x3f86c21d65]
   /usr/bin/perl[0x400d61]
  
  
   This is also not 100% consistent. I got it to do a restore once. Doing
   the same steps with the same disk and date will not restore, it is all
   the above.
  
   Any ideas?

 Looks like there was some build problem perhaps and $PS is not defined
 in Constants.pm

 locate Constants.pm | grep Amanda | xargs grep -i ps
 =head1 SYNOPSIS
 $PS = /bin/ps;
 $PS_ARGUMENT = -eo pid,ppid,command;


Thank you! That was it. I will be filing this with Fedora for a rebuild.

Thanks again,
Trever



signature.asc
Description: OpenPGP digital signature


Re: Can amanda backup cause/contribute to a system 'freeze' in Linux

2011-07-23 Thread Trever L. Adams
On 7/23/2011 8:05 AM, Leo Subscriptions wrote:
 I'm running Ubuntu 11.04 (64 bit) and experience the occasional
 'system freeze'. By freeze I mean a complete freeze of the system (ie.
 no system log entries, but system [ie. disks] is still running).

 I have reported this is an Ubuntu bug a while ago, but have noticed
 that the three times this has happened an amanda backup was running. I
 even moved the time of the backup to prove the point

 I'm running a RAID1, with one of my folders encrypted. Both the
 holding disk and final backup disk are single disks.

 My question is if anybody could think that amanada could be the
 contributing factor for the failure and if so how.


By chance are you using r8169? If so, that may be it. It was causing all
sorts of hard locks and soft locks.

Trever


signature.asc
Description: OpenPGP digital signature


Re: Can amanda backup cause/contribute to a system 'freeze' in Linux

2011-07-23 Thread Trever L. Adams
I'm almost positive the problem is the network card. I would suggest trying a 
tg3 or an e1000 based card. it fixed my problems.
-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

Leo Subscriptions llsub...@zudiewiener.com wrote:

Following are some of details of my system

Motherboadr: Gigabyte GA-MA790FXT-UD5P
CPU: AMD Phentom II X4 (4 CPUs)
Memeory: 4BG
Disks: All Western Digital drives, with 2TB Raid 1, 2 TB disk used for backup 
storage, 1TB  holding, all SMART enabled and monitored
Network: Realtek RTL811/8168B PCI Express Gigabit Controller (rev 02)



On Sat, 2011-07-23 at 08:39 -0600, Trever L. Adams wrote:

On 7/23/2011 8:05 AM, Leo Subscriptions wrote: 

I'm running Ubuntu 11.04 (64 bit) and experience the occasional 'system 
freeze'. By freeze I mean a complete freeze of the system (ie. no system log 
entries, but system [ie. disks] is still running).

I have reported this is an Ubuntu bug a while ago, but have noticed that the 
three times this has happened an amanda backup was running. I even moved the 
time of the backup to prove the point

I'm running a RAID1, with one of my folders encrypted. Both the holding disk 
and final backup disk are single disks.

My question is if anybody could think that amanada could be the contributing 
factor for the failure and if so how.


By chance are you using r8169? If so, that may be it. It was causing all sorts 
of hard locks and soft locks.

Trever




[SOLVED?] Re: BUG REPORT: amgtar not working

2011-04-28 Thread Trever L. Adams
On 04/20/2011 08:04 AM, Trever L. Adams wrote:
 I have a setup. Using user-tar from the templates (maybe only Fedora
 supplied, I don't know) as the base for my backup, things work fine and
 tar runs as root.

 When changing to a type amgtar and dt_amgtar (again templates on my
 system) things do not work. tar runs as user 33 (amandabackup). uid and
 euid are 33. Please, see attached log files for the information.

 Thank you for any help on figuring this out and fixing things.

 Trever
This bug appears to have been a Fedora packaging bug.
https://bugzilla.redhat.com/show_bug.cgi?id=697933

Whether or not it is the right solution, amgtar has been setuid root and
only allowed to be run by root and disk group (which amandabackup user
is part of).

Thank you for all who have been involved in fixing the problem.

Trever
-- 
All who joy would win Must share it -- Happiness was born a twin. --
Lord Byron



signature.asc
Description: OpenPGP digital signature


Re: amgtar set_euid Fixed Bug Broken Again

2011-04-20 Thread Trever L. Adams
On 04/19/2011 11:46 AM, Jean-Louis Martineau wrote:
 The fix is already committed.

 If you have a similar problem, then make a new bug report with all
 relevant information including the amgtar debug file.

 Jean-Louis
Pardon me for not readily knowing, where would be the proper place to
file a bug report. I have the files now.
-- 
Seize the day, put no trust in the morrow! -- Quintus Horatius Flaccus
(Horace)



signature.asc
Description: OpenPGP digital signature


amgtar set_euid Fixed Bug Broken Again

2011-04-19 Thread Trever L. Adams
Please reference:
http://old.nabble.com/Re%3A-amgtar-getting-Permission-denied-td28223185.html

With Amanda 3.2.2 I am getting the symptom described in the web page
above. I also notice that estimate, backup and restore code paths all
are missing the appropriate seteuid(0)/setuid(0) code.

Would someone with commit access on the community edition please commit
the appropriate fix?

Thank you,
Trever Adams




signature.asc
Description: OpenPGP digital signature


kerberos and Amanda

2011-04-16 Thread Trever L. Adams
For technical reasons, I have a set of hosts I must backup. They are in
different kerberos realms. The realms cannot and do not trust each other
(hopefully the technical reasons for this will be solved someday).

Can krb5keytab and krb5principal be defined in a dumptype or some other
way so that I can have them all defined in one amanda.conf? I need to
fit as many hosts on each tape as possible, so I cannot have different
dump sets (at least if I understand the documentation correctly, I am
new to amanda).

Thank you,
Trever
-- 
What makes his world so hard to see clearly is not its strangeness but
its usualness. Familiarity can blind you. -- Robert M. Pirsig




signature.asc
Description: OpenPGP digital signature


Re: kerberos and Amanda

2011-04-16 Thread Trever L. Adams
On 04/16/2011 01:10 PM, Christ Schlacta wrote:
 Also note:  its never wise to backup across intrusted domain boundaries.  
 They're intrusted for a reason.

 Jean-Louis Martineau martin...@zmanda.com wrote:

In this case, it is purely a technical reason (Samba 4 doesn't do trusts
yet). If that were not the case, they would trust each other. Thank you
for the tip.


Trever
-- 
The idea that Bill Gates has appeared like a knight in shining armour
to lead all customers out of a mire of technological chaos neatly
ignores the fact that it was he who, by peddling second-rate technology,
led them into it in the first place. -- Douglas Adams, on Windows '95.



signature.asc
Description: OpenPGP digital signature