I am able to restore the Odoo database on one of our cloud Ubuntu instances. But while referring to that application in Odoo Conf file, we are getting the below error. Same database is working fine in local environment
File "/usr/lib/python3.8/socketserver.py", line 466, in server_bind
self.socket.bind(self.server_address)
OSError: [Errno 98] Address already in use
2021-03-02 19:16:03,134 7351 ERROR ? odoo.sql_db: bad query: CREATE SEQUENCE base_registry_signaling INCREMENT BY 1 START WITH 1
ERROR: relation "base_registry_signaling" already exists
2021-03-02 19:16:03,278 7351 ERROR ? odoo.modules.registry: Failed to load registry
2021-03-02 19:16:03,281 7351 CRITICAL ? odoo.service.server: Failed to initialize database databasename.
Traceback (most recent call last):
File "/home/odoo2/odoo-12/odoo/service/server.py", line 1162, in preload_registries
registry = Registry.new(dbname, update_module=update_module)
File "/home/odoo2/odoo-12/odoo/modules/registry.py", line 83, in new
registry.setup_signaling()
File "/home/odoo2/odoo-12/odoo/modules/registry.py", line 378, in setup_signaling
cr.execute("CREATE SEQUENCE base_registry_signaling INCREMENT BY 1 START WITH 1")
File "/home/odoo2/odoo-12/odoo/sql_db.py", line 148, in wrapper
return f(self, *args, **kwargs)
File "/home/odoo2/odoo-12/odoo/sql_db.py", line 225, in execute
res = self._obj.execute(query, params)
psycopg2.errors.DuplicateTable: relation "base_registry_signaling" already exists
I just stumbled on the same problem.
Turns out I dumped the db with the --no-owner option and on import it set the owner to the current user - which was different.
Try setting the owner of the db and tables to the user your're using for odoo.
ALTER DATABASE "db_name" OWNER TO user;
-- Assign everything in the currently selected db to 'user'.
REASSIGN OWNED BY other_user TO user;
you also using a command line to restore odoo database in any verison:
curl -F 'master_pwd=superadmin_passwd' -F backup_file=#/opt/odoo/odoo_backups/db1.2018-04-14.zip -F 'copy=true' -F 'name=db3' http://localhost:8069/web/database/restore
Use above command you using restore your odoo database:
Example like :
curl -F 'master_pwd=admin1' -F backup_file=#/home/dell/backup_dir/back_up_filename.zip -F 'copy=true' -F 'name=db3' http://localhost:8069/web/database/restore
In the example above our the Master Password is ADMIN_PASSWORD and we are creating a backup file back_up_filename.zip of a database named DB_NAME which will be saved in the backup_dir directory.
Note: Depending on the database size and your Internet speed, the restoration process may take some time.
Related
I'm trying run redis/yedis on the yugabyte database by following https://docs.yugabyte.com/latest/yedis/quick-start/#linux.
I run the command ./bin/yb-ctl setup_redis but I end up with the error:
Setting up YugaByte DB support for Redis API.
Waiting for cluster to be ready.
Traceback (most recent call last):
File "./bin/yb-ctl", line 2104, in <module>
control.run()
File "./bin/yb-ctl", line 2081, in run
self.args.func()
File "./bin/yb-ctl", line 1967, in setup_redis_cmd_impl
self.wait_for_cluster_or_raise()
File "./bin/yb-ctl", line 1646, in wait_for_cluster_or_raise
if not self.wait_for_cluster():
File "./bin/yb-ctl", line 1591, in wait_for_cluster
cmd_list_tservers = self.yb_admin_cmd_list("list_all_tablet_servers")
File "./bin/yb-ctl", line 2036, in yb_admin_cmd_list
raise ValueError("Cannot form yb-admin command without knowing master addresses")
ValueError: Cannot form yb-admin command without knowing master addresses
Viewing file /tmp/tmpbg32mn95:
^^^ Encountered errors ^^^
2021-12-22 16:08:27,463 INFO: Waiting for master and tserver processes to come up.
I have my master and tserver both running after running the commands:
./bin/yb-master --flagfile master.conf >& /home/doug/mark/disk1/yb-master.out &
./bin/yb-tserver --flagfile tserver.conf >& /home/doug/mark/yb-tserver.out&
The master config file:
--master_addresses=192.168.1.62:7100
--rpc_bind_addresses=192.168.1.62:7100
--fs_data_dirs=/home/doug/mark/disk1
The tserver config file:
--tserver_master_addrs=192.168.1.62:7100
--rpc_bind_addresses=192.168.1.62:9100
--start_pgsql_proxy
--pgsql_proxy_bind_address=192.168.1.62:5433
--cql_proxy_bind_address=192.168.1.62:9042
--fs_data_dirs=/home/doug/mark/disk1
and in the master log I can see:
I1223 00:08:03.023463 1527298 heartbeater.cc:340] P 419a60d5690945c8ad23c42f7ba758ba: Connected to a leader master server at 192.168.1.62:7100
I1223 00:08:03.023666 1527298 heartbeater.cc:388] P 419a60d5690945c8ad23c42f7ba758ba: Registering TS with master...
But I'm not sure why I can't start up the redis-cli based on the tutorial link above?
Since you're running the yb-tserver & yb-master manually, try running this command:
./bin/yb-admin [-master_addresses server1:port,server2:port,server3:port,...] setup_redis_table
Note that YEDIS API is not a focus, it must be viewed as a deprecated API for new application development purposes. (docs link)
I am trying to run gem5 in FS mode. It works fine. But If I switch to super user(using sudo su) and then try then I get below error-
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/home/test/gem5/src/python/m5/main.py", line 435, in main
exec filecode in scope
File "configs/example/fs.py", line 344, in <module>
test_sys = build_test_system(np)
File "configs/example/fs.py", line 99, in build_test_system
options.ruby, cmdline=cmdline)
File "/home/test/gem5/configs/common/FSConfig.py", line 637, in makeLinuxX86System
makeX86System(mem_mode, numCPUs, mdesc, self, Ruby)
File "/home/test/gem5/configs/common/FSConfig.py", line 562, in makeX86System
disk0.childImage(mdesc.disk())
File "/home/test/gem5/configs/common/Benchmarks.py", line 58, in disk
return disk(self.diskname)
File "/home/test/gem5/configs/common/SysPaths.py", line 58, in __call__
raise IOError, "Can't find a path to system files."
IOError: Can't find a path to system files.
Any lead??
First, avoid running gem5 as with sudo/as root if you can, for the same reasons as any other programs.
I would guess that the command through sudo is not seeing the M5_PATH environment variable: How to keep environment variables when using sudo Can you ensure that the variable is visible to the executable?
Finally, as mentioned at Gem 5 IOError: Can't find a path to system files. Full System X86 simulation setup M5_PATH is not needed anymore, so I would really just never use it, and just explicitly point to the files gem5 needs with the command line options.
I try to restore my backup from amazon using the following command as example
duplicity restore --sign-key '7F73FA36' --encrypt-key '5FD0100F' scp://rich#backup_server//mnt/backups/edge/main
and shell returns the following error
"Import of duplicity.backends.dpbxbackend Failed: No module named dropbox
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1466, in <module>
with_tempdir(main)
File "/usr/bin/duplicity", line 1459, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1312, in main"
Any advice will greatly help.
If you do not want to store backups in Dropbox, i suppose that this can be ignored.
I wondered the same as you, and looked a bit: it seems to me that Duplicity tries to load a Dropbox backend. See in /usr/lib64/python2.6/site-packages/duplicity/backends/dpbxbackend.py, there is a line from dropbox import client, rest, session
As i do not have this Python Dropbox library installed, it can not find it, but does not prevent me to use Duplicity for other backends
You may install dropbox python client by running
root#host# pip install dropbox2
I saw this exception when I was testing pika
It works when I was using only defaults. However it threw an exception when I added credentials in the connection parameters.
import pika
credentials = pika.PlainCredentials('foo', 'bar')
connection = pika.BlockingConnection(pika.ConnectionParameters(host='localhost', credentials=credentials))
channel = connection.channel()
channel.queue_declare(queue='device_presence_info')
print ' [*] Waiting for messages. To exit press CTRL+C'
def callback(ch, method, properties, body):
print " [x] Received %s" % body
channel.basic_consume(callback,
queue='device_presence_info',
no_ack=True)
channel.start_consuming()
It gave me this error:
ubuntu#SDNS:~/lang/python/pika$ python receive.py
Traceback (most recent call last):
File "receive.py", line 12, in <module>
connection = pika.BlockingConnection(pika.ConnectionParameters(host='54.241.122.167', credentials=credentials))
File "/usr/local/lib/python2.6/dist-packages/pika/adapters/blocking_connection.py", line 107, in __init__
super(BlockingConnection, self).__init__(parameters, None, False)
File "/usr/local/lib/python2.6/dist-packages/pika/adapters/base_connection.py", line 62, in __init__
on_close_callback)
File "/usr/local/lib/python2.6/dist-packages/pika/connection.py", line 590, in __init__
self.connect()
File "/usr/local/lib/python2.6/dist-packages/pika/adapters/blocking_connection.py", line 206, in connect
if not self._adapter_connect():
File "/usr/local/lib/python2.6/dist-packages/pika/adapters/blocking_connection.py", line 275, in _adapter_connect
raise exceptions.AMQPConnectionError(1)
pika.exceptions.AMQPConnectionError: 1
Can any help me ? Thanks.
That error normally means that either your credentials are wrong, or that the user you created doesn't have access to the exchange / queue you're trying to access. When creating the user, make sure to give access to the resources you're going to be using (or, if it's just for testing, to everything the same way the 'guest' account has). You can do this via the management plugin or the command line.
This post has a good sample on how to set the different permissions using the management plugin.
Install RabbitMQ server (for Debian/Ubuntu):
sudo apt-get install rabbitmq-server
We have an auto-deployment script that uses wsadmin and jython. The script appears to work as expected however after 6-7 redeployments the AdminTask object becomes unavilable, resulting in the following error when we attempt to use that object:
WASX7209I: Connected to process "server1" on node ukdlniqa41Node01 using SOAP connector; The type of process is: UnManagedProcess
WASX8011W: AdminTask object is not available.
...
Traceback (innermost last):
File "<string>", line 251, in ?
File "<string>", line 14, in main
File "<string>", line 38, in initialize
NameError: AdminTask
My question is, what would cause this AdminTask object to become unavailable? (it remains unavailable until we restart the server instance)
AdminTask may be available if one of the previous tasks does not finish properly. This happens often especially if your server is in development mode. I would suggest gathering Deployment Mustgather as per http://www-01.ibm.com/support/docview.wss?rs=180&context=SSCR4XA&q1=MustGatherDocument&uid=swg21199344&loc=en_US&cs=utf-8&lang=en and submitting the results to IBM.