[ovirt-users] Re: change broker.conf configuration on shared storage

[emanuel . santosvarina]

Simon, that works, thanks!  Whish list: edit the configuration from the 
web UI ;-)

--
Emanuel



Von:Simone Tiraboschi 
An: emanuel.santosvar...@mahle.com, 
Kopie:  users 
Datum:  06.10.2016 12:17
Betreff:Re: [ovirt-users] change broker.conf configuration on 
shared storage





On Wed, Oct 5, 2016 at 4:29 PM,  wrote:
hi all, 

hmm, broker.conf is now on the shared storage and not replicated on each 
host local file system. how to make changes to the conf, e.g.  the notify 
key? 

You can use something like what is documented here:
https://bugzilla.redhat.com/show_bug.cgi?id=1366879#c23

Instead of fixing fhanswers.conf as in that script, you have to fix 
broker.conf 

 

thanks, emanuel 


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users



--
IMPORTANT!
This message has been scanned for viruses and phishing links.
However, it is your responsibility to evaluate the links and attachments you 
choose to click.
If you are uncertain, we always try to help.
Greetings helpd...@actnet.se



--
IMPORTANT!
This message has been scanned for viruses and phishing links.
However, it is your responsibility to evaluate the links and attachments you 
choose to click.
If you are uncertain, we always try to help.
Greetings helpd...@actnet.se


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/UKY43MCD62NMASCUFLQHBUUCNX62FHUU/

[ovirt-users] change broker.conf configuration on shared storage

[emanuel . santosvarina]

hi all, 

hmm, broker.conf is now on the shared storage and not replicated on each 
host local file system. how to make changes to the conf, e.g.  the notify 
key? 

thanks, emanuel


--
IMPORTANT!
This message has been scanned for viruses and phishing links.
However, it is your responsibility to evaluate the links and attachments you 
choose to click.
If you are uncertain, we always try to help.
Greetings helpd...@actnet.se



--
IMPORTANT!
This message has been scanned for viruses and phishing links.
However, it is your responsibility to evaluate the links and attachments you 
choose to click.
If you are uncertain, we always try to help.
Greetings helpd...@actnet.se


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/KL2U36RKESMNWO6J7JN5SB2T7LCNR5VA/

[ovirt-users] Antwort: Re: Antwort: Re: vacuumdb: could not connect to database ovirt_engine_history

[emanuel . santosvarina]

Hi Shirly,

here you are:

--snip
ovirt_engine_history=# SELECT * FROM history_configuration;
 var_name  | var_value |  var_datetime 
---+---+
 default_language  | en_US | 
 firstSync | false | 2018-04-09 15:52:00+02
 MinimalETLVersion | 4.2.0 | 
 lastHourAggr  |   | 2018-07-03 12:00:00+02
 HourlyAggFailed   | false | 
 lastDayAggr   |   | 2018-07-02 00:00:00+02
(6 rows)

ovirt_engine_history=# 
--snap

date
Tue Jul  3 13:16:27 CEST 2018

Thanky you,
Ema




Von:"Shirly Radco" 
An: emanuel.santosvar...@mahle.com, 
Kopie:  "Roy Golan" , "users" 
Datum:  03.07.2018 12:37
Betreff:Re: [ovirt-users] Antwort: Re: vacuumdb: could not connect 
to database ovirt_engine_history



Hi,

Please share your history_configuration table content 
in ovirt_engine_history db:

SELECT * FROM history_configuration;

the date and time you run this query

and the ovirt_engine_dwh.log





--
SHIRLY RADCO
BI SeNIOR SOFTWARE ENGINEER
Red Hat Israel


TRIED. TESTED. TRUSTED.

On Fri, Jun 29, 2018 at 9:06 AM,  wrote:
Hi Roy, well db is alive : 


su - postgres -c 'scl enable rh-postgresql95 -- psql ovirt_engine_history' 

psql (9.5.9) 
Type "help" for help. 

ovirt_engine_history=# \dt 
 List of relations 
 Schema |   Name| Type  |Owner 

+---+---+-- 

 public | calendar  | table | ovirt_engine_history 

 public | cluster_configuration | table | ovirt_engine_history 

 public | datacenter_configuration  | table | ovirt_engine_history 

 public | datacenter_storage_domain_map | table | ovirt_engine_history 

 public | enum_translator   | table | ovirt_engine_history 

 public | history_configuration | table | ovirt_engine_history 

 public | host_configuration| table | ovirt_engine_history 

 public | host_daily_history| table | ovirt_engine_history 

 public | host_hourly_history   | table | ovirt_engine_history 

 public | host_interface_configuration  | table | ovirt_engine_history 

 public | host_interface_daily_history  | table | ovirt_engine_history 

 public | host_interface_hourly_history | table | ovirt_engine_history 

 public | host_interface_samples_history| table | ovirt_engine_history 

 public | host_samples_history  | table | ovirt_engine_history 

 public | schema_version| table | ovirt_engine_history 

 public | statistics_vms_users_usage_daily  | table | ovirt_engine_history 

 public | statistics_vms_users_usage_hourly | table | ovirt_engine_history 

 public | storage_domain_configuration  | table | ovirt_engine_history 

 public | storage_domain_daily_history  | table | ovirt_engine_history 

 public | storage_domain_hourly_history | table | ovirt_engine_history 

 public | storage_domain_samples_history| table | ovirt_engine_history 

 public | tag_details   | table | ovirt_engine_history 

 public | tag_relations_history | table | ovirt_engine_history 

 public | users_details_history | table | ovirt_engine_history 

 public | vm_configuration  | table | ovirt_engine_history 

 public | vm_daily_history  | table | ovirt_engine_history 

 public | vm_device_history | table | ovirt_engine_history 

 public | vm_disk_configuration | table | ovirt_engine_history 

 public | vm_disk_daily_history | table | ovirt_engine_history 

 public | vm_disk_hourly_history| table | ovirt_engine_history 

 public | vm_disk_samples_history   | table | ovirt_engine_history 

 public | vm_disks_usage_daily_history  | table | ovirt_engine_history 

 public | vm_disks_usage_hourly_history | table | ovirt_engine_history 

 public | vm_disks_usage_samples_history| table | ovirt_engine_history 

 public | vm_hourly_history | table | ovirt_engine_history 

 public | vm_interface_configuration| table | ovirt_engine_history 

 public | vm_interface_daily_history| table | ovirt_engine_history 

 public | vm_interface_hourly_history   | table | ovirt_engine_history 

 public | vm_interface_samples_history  | table | ovirt_engine_history 

 public | vm_samples_history| table | ovirt_engine_history 

(40 rows) 

ovirt_engine_history=# 






Von:"Roy Golan"  
An:emanuel.santosvar...@mahle.com, 
Kopie:users@ovirt.org 
Datum:28.06.2018 17:37 
Betreff:Re: [ovirt-users] vacuumdb: could not connect to database 
ovirt_engine_history 






On Thu, 28 Jun 2018 at 18:06  wrote: 
..trying to update from 4.2.3 to 4.2.4 engine-setup fails with the 
following error: 

--snip 

[ovirt-users] Antwort: Re: vacuumdb: could not connect to database ovirt_engine_history

[emanuel . santosvarina]

Hi Roy, well db is alive :


su - postgres -c 'scl enable rh-postgresql95 -- psql ovirt_engine_history'
psql (9.5.9)
Type "help" for help.

ovirt_engine_history=# \dt
 List of relations
 Schema |   Name| Type  |Owner 
+---+---+--
 public | calendar  | table | ovirt_engine_history
 public | cluster_configuration | table | ovirt_engine_history
 public | datacenter_configuration  | table | ovirt_engine_history
 public | datacenter_storage_domain_map | table | ovirt_engine_history
 public | enum_translator   | table | ovirt_engine_history
 public | history_configuration | table | ovirt_engine_history
 public | host_configuration| table | ovirt_engine_history
 public | host_daily_history| table | ovirt_engine_history
 public | host_hourly_history   | table | ovirt_engine_history
 public | host_interface_configuration  | table | ovirt_engine_history
 public | host_interface_daily_history  | table | ovirt_engine_history
 public | host_interface_hourly_history | table | ovirt_engine_history
 public | host_interface_samples_history| table | ovirt_engine_history
 public | host_samples_history  | table | ovirt_engine_history
 public | schema_version| table | ovirt_engine_history
 public | statistics_vms_users_usage_daily  | table | ovirt_engine_history
 public | statistics_vms_users_usage_hourly | table | ovirt_engine_history
 public | storage_domain_configuration  | table | ovirt_engine_history
 public | storage_domain_daily_history  | table | ovirt_engine_history
 public | storage_domain_hourly_history | table | ovirt_engine_history
 public | storage_domain_samples_history| table | ovirt_engine_history
 public | tag_details   | table | ovirt_engine_history
 public | tag_relations_history | table | ovirt_engine_history
 public | users_details_history | table | ovirt_engine_history
 public | vm_configuration  | table | ovirt_engine_history
 public | vm_daily_history  | table | ovirt_engine_history
 public | vm_device_history | table | ovirt_engine_history
 public | vm_disk_configuration | table | ovirt_engine_history
 public | vm_disk_daily_history | table | ovirt_engine_history
 public | vm_disk_hourly_history| table | ovirt_engine_history
 public | vm_disk_samples_history   | table | ovirt_engine_history
 public | vm_disks_usage_daily_history  | table | ovirt_engine_history
 public | vm_disks_usage_hourly_history | table | ovirt_engine_history
 public | vm_disks_usage_samples_history| table | ovirt_engine_history
 public | vm_hourly_history | table | ovirt_engine_history
 public | vm_interface_configuration| table | ovirt_engine_history
 public | vm_interface_daily_history| table | ovirt_engine_history
 public | vm_interface_hourly_history   | table | ovirt_engine_history
 public | vm_interface_samples_history  | table | ovirt_engine_history
 public | vm_samples_history| table | ovirt_engine_history
(40 rows)

ovirt_engine_history=# 






Von:"Roy Golan" 
An: emanuel.santosvar...@mahle.com, 
Kopie:  users@ovirt.org
Datum:  28.06.2018 17:37
Betreff:Re: [ovirt-users] vacuumdb: could not connect to database 
ovirt_engine_history





On Thu, 28 Jun 2018 at 18:06  wrote:
..trying to update from 4.2.3 to 4.2.4 engine-setup fails with the 
following error: 

--snip 
2018-06-28 16:26:45,507+0200 DEBUG 
otopi.plugins.ovirt_engine_setup.ovirt_engine_dwh.db.vacuum 
plugin.execute:926 execute-output: 
['/usr/share/ovirt-engine-dwh/bin/dwh-vacuum.sh', '-f', '-v'] stderr: 
vacuumdb: could not connect to database ovirt_engine_history: FATAL: 
 password authentication failed for user "ovirt_engine_history" 

do you have dwh installed? if no just skip this vacuum part.
you can check the db connection from cli using
$ su - postgres -c 'scl enable rh-postgresql95 -- psql 
ovirt-engine-history'

2018-06-28 16:26:45,507+0200 DEBUG otopi.context 
context._executeMethod:143 method exception 
Traceback (most recent call last): 
  File "/usr/lib/python2.7/site-packages/otopi/context.py", line 133, in 
_executeMethod 
method['method']() 
  File 
"/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine-dwh/db/vacuum.py",
 
line 126, in _vacuum 
self.execute(args=args) 
  File "/usr/lib/python2.7/site-packages/otopi/plugin.py", line 931, in 
execute 
command=args[0], 
RuntimeError: Command '/usr/share/ovirt-engine-dwh/bin/dwh-vacuum.sh' 
failed to execute 
2018-06-28 16:26:45,508+0200 ERROR otopi.context 
context._executeMethod:152 Failed to execute stage 'Misc configuration': 
Command 

[ovirt-users] vacuumdb: could not connect to database ovirt_engine_history

[emanuel . santosvarina]

..trying to update from 4.2.3 to 4.2.4 engine-setup fails with the 
following error:

--snip
2018-06-28 16:26:45,507+0200 DEBUG 
otopi.plugins.ovirt_engine_setup.ovirt_engine_dwh.db.vacuum 
plugin.execute:926 execute-output: 
['/usr/share/ovirt-engine-dwh/bin/dwh-vacuum.sh', '-f', '-v'] stderr:
vacuumdb: could not connect to database ovirt_engine_history: FATAL: 
password authentication failed for user "ovirt_engine_history"

2018-06-28 16:26:45,507+0200 DEBUG otopi.context 
context._executeMethod:143 method exception
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/otopi/context.py", line 133, in 
_executeMethod
method['method']()
  File 
"/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine-dwh/db/vacuum.py",
 
line 126, in _vacuum
self.execute(args=args)
  File "/usr/lib/python2.7/site-packages/otopi/plugin.py", line 931, in 
execute
command=args[0],
RuntimeError: Command '/usr/share/ovirt-engine-dwh/bin/dwh-vacuum.sh' 
failed to execute
2018-06-28 16:26:45,508+0200 ERROR otopi.context 
context._executeMethod:152 Failed to execute stage 'Misc configuration': 
Command '/usr/share/ovirt-engine-dwh/bin/dwh-vacuum.sh' failed to execute
2018-06-28 16:26:45,508+0200 DEBUG otopi.transaction transaction.abort:119 
aborting 'Yum Transaction'
--snap

Any ideas?

Thank You,
Ema___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/HGQJQ4LME5Y3YELU46GRDT6QS4SJUAQ6/

[ovirt-users] Antwort: Re: get UI working throug ALIAS and real hostname

[emanuel . santosvarina]

GREAT! THANKS a lot ..



Von:Juan Hernández 
An: emanuel.santosvar...@mahle.com, users@ovirt.org, 
Datum:  24.01.2017 15:41
Betreff:Re: [ovirt-users] get UI working throug ALIAS and real 
hostname



On 01/24/2017 03:15 PM, emanuel.santosvar...@mahle.com wrote:
> If I access the UI via "ALIAS" I get the Error-Page "The client is not
> authorized to request an authorization. It's required to access the
> system using FQDN.
> 
> What can I do to get UI working through ALIAS and real hostname?
> 
> Thx,
> Emanuel
> 

Create a 99-whatever-you-like.conf file in
/etc/ovirt-engine/engine.conf.d with the following content:

  SSO_ALTERNATE_ENGINE_FQDNS="thealias"

Then restart the engine:

  systemctl restart ovirt-engine

This setting is documented here:


https://github.com/oVirt/ovirt-engine/blob/master/packaging/services/ovirt-engine/ovirt-engine.conf.in#L363-L366



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] get UI working throug ALIAS and real hostname

[emanuel . santosvarina]

If I access the UI via "ALIAS" I get the Error-Page "The client is not 
authorized to request an authorization. It's required to access the system 
using FQDN.

What can I do to get UI working through ALIAS and real hostname?

Thx,
Emanuel___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] change broker.conf configuration on shared storage

[emanuel . santosvarina]

Simon, that works, thanks!  Whish list: edit the configuration from the 
web UI ;-)

--
Emanuel



Von:Simone Tiraboschi 
An: emanuel.santosvar...@mahle.com, 
Kopie:  users 
Datum:  06.10.2016 12:17
Betreff:Re: [ovirt-users] change broker.conf configuration on 
shared storage





On Wed, Oct 5, 2016 at 4:29 PM,  wrote:
hi all, 

hmm, broker.conf is now on the shared storage and not replicated on each 
host local file system. how to make changes to the conf, e.g.  the notify 
key? 

You can use something like what is documented here:
https://bugzilla.redhat.com/show_bug.cgi?id=1366879#c23

Instead of fixing fhanswers.conf as in that script, you have to fix 
broker.conf 

 

thanks, emanuel 


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] change broker.conf configuration on shared storage

[emanuel . santosvarina]

hi all, 

hmm, broker.conf is now on the shared storage and not replicated on each 
host local file system. how to make changes to the conf, e.g.  the notify 
key? 

thanks, emanuel

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Antwort: Re: Backup of vm

[emanuel . santosvarina]

Hi, 

even  online fullbackup's, e.g. :

https://github.com/wefixit-AT/oVirtBackup


Tschau,
Emanuel



Von:Fred Rolland 
An: Budur Nagaraju , 
Kopie:  users 
Datum:  08.12.2015 10:08
Betreff:Re: [ovirt-users] Backup of vm
Gesendet von:   users-boun...@ovirt.org



Hi,

You can take a look at Backup/Restore API [1].
You can also export the VM and disks to an export domain. (The VM needs to 
be down)

Regards,

Fred

[1] http://www.ovirt.org/Features/Backup-Restore_API_Integration

On Tue, Dec 8, 2015 at 10:18 AM, Budur Nagaraju  wrote:
HI 


Pls let me know how to take backup of vms and restore in oVirt ?

Thanks,
Nagaraju


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users