Hello:
I have a very old local taiga install (5.0.12 according to the CHANGELOG). Upgrade does not work. Dump to json does not work (neither from the web, not from command line)
It is not crucial to migrate, but it would be nice to keep some kind of backup.
A wget or curl dump would be enough, but I cannot make login work. I have tried to get the cookies with two browser extensions, wget and curl, but they seem to be empty:
Care to give a hint? Thank you
Have you tried incremental upgrades?
Thanks! Yes, I followed the procedure a few years ago. The procedure started fine but eventually some step did not work. I don’t remember the details, but I couldn’t proceed from 5.0.12.
At this point, the install abandoned and all, a dump of the old site and the public taiga would be perfect.
Is the site running?
Do you have a copy of the postgres database?
Do you have a copy of the old taiga-back files?
Do you have a copy of the old taiga-front files?
Is it a docker install?
Is the site running?
Do you have a copy of the postgres database?
Do you have a copy of the old taiga-back files?
Do you have a copy of the old taiga-front files?
Yes!
Is it a docker install?
No, the migration went bad before the migration to docker.
Hi there,
When you say the dump does not work, do you mean it does not get generated or that it get’s generated wrong and is not accepted in the newer instance? And if it errors out, could you share the logs?
If it’s the former you should check if you have the celery services running and the queues are picking up the job. If it’s the latter you could migrate “manually” via an intermediate script that gets data from the old instance via API and writes it via API as well to the new instance. Attachments I think would be a bit of a pain though.
Best!
It does not generate a dump. Where are the logs? I hit the export button and I just get a message. Can’t find the errors in the server :-/
Well, it depends on how you installed it, but the install instructions without docker use systemd units, so sudo journalctl -u taiga-back or taiga, or taiga-celery, depends on how your unit is called.
Best!
The only sustemd unit with “taiga” or “celery” in it is “taiga-back“, and
# journalctl -u taiga.service
-- No entries --
:-/
Do you have command line/ssh root/taiga access to the server?
If yes, can you start a Django session?
Is the server running?
If yes, where?
Do you have command line/ssh root/taiga access to the server?
Yes
If yes, can you start a Django session?
I was able, and I got the error when trying to get the dump, but after pip install upgrading the virtualenv, I can no longer, and get this error:
Trying import local.py settings...
Traceback (most recent call last):
File "/home/taiga/.virtualenvs/taiga/lib/python3.5/site-packages/django/apps/config.py", line 118, in create
cls = getattr(mod, cls_name)
AttributeError: module 'taiga.base' has no attribute 'api'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/taiga/taiga-back/taiga/base/api/settings.py", line 205, in import_from_string
module = importlib.import_module(module_path)
File "/home/taiga/.virtualenvs/taiga/lib/python3.5/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 986, in _gcd_import
File "<frozen importlib._bootstrap>", line 969, in _find_and_load
File "<frozen importlib._bootstrap>", line 958, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 673, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 665, in exec_module
File "<frozen importlib._bootstrap>", line 222, in _call_with_frames_removed
File "/home/taiga/taiga-back/taiga/base/throttling.py", line 23, in <module>
from ipware.ip import get_ip
ImportError: cannot import name 'get_ip'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "manage.py", line 29, in <module>
execute_from_command_line(sys.argv)
File "/home/taiga/.virtualenvs/taiga/lib/python3.5/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line
utility.execute()
File "/home/taiga/.virtualenvs/taiga/lib/python3.5/site-packages/django/core/management/__init__.py", line 357, in execute
django.setup()
File "/home/taiga/.virtualenvs/taiga/lib/python3.5/site-packages/django/__init__.py", line 24, in setup
apps.populate(settings.INSTALLED_APPS)
File "/home/taiga/.virtualenvs/taiga/lib/python3.5/site-packages/django/apps/registry.py", line 91, in populate
app_config = AppConfig.create(entry)
File "/home/taiga/.virtualenvs/taiga/lib/python3.5/site-packages/django/apps/config.py", line 136, in create
import_module(entry)
File "/home/taiga/.virtualenvs/taiga/lib/python3.5/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 986, in _gcd_import
File "<frozen importlib._bootstrap>", line 969, in _find_and_load
File "<frozen importlib._bootstrap>", line 958, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 673, in _load_unlocked
Is the server running?
It does run, never stopped 
!
If yes, where?
I guess it’s safe to share the url, isn’t it? It’s outdated, but registration is not open, and there’s nothing of value in there…
Regards!
You’d have to lock the requirements file to use the versions that were in place then redo pip install.
Then cd into the same directory as the virtual environment then activate it.
I would not reboot based on the error logs.
then why are you going through the pain if trying to export.
I’d use the api’s or dump projects as json if that works.
Or just rebuild manually.
Cheers
Keith
then why are you going through the pain if trying to export.
Sorry for the delay, somehow my answer was not sent correctly: Should have said there are no secrets in that server, but there is valuable info we’d like to keep, even if it has to be a static version…
I’d use the api’s or dump projects as json if that works.
Yeah, sure, tried that a long time ago, tried again these days, but no luck 
The site was really crumbling, specially after the latest attempts to pip install upgrade . Some pages would come out as a blank template 90% of the time 
, but reloading the page again and again would eventually work. It wouldn’t have survived a restart. A dump seemed like the safe choice.
I finally got a dump with `playwright`. Had to tune it to really get everything, then use a few regex to rewire the links, and it looks nice now.
We will now start fresh, and keep the dump for reference.
Thanks again for your time. Real sorry I wasn’t able to follow all your suggestions, but I couldn’t get the venv right…
Good to hear you sorted it out. Using Playwright is a very interesting solution. Well done!
Cheers
Keith
