phreeq

I'm using binhex/arch-urbackup:2.5.33-2-01

I went and pulled version 2.5.33-2-01, which is admittedly an old version, and it's running now. I'll keep an eye on the repository and see if a new update rolls out that may fix this issue.

I'm having the same issue

After completing the parity check from the last startup, I pulled the USB drive and ran a check with Disk Utility. It didn't find any problems, so I'm guessing that the USB drive isn't the source of the problem.

The system may have been semi-crashed when I grabbed the last set of diagnostics, but this should be a good set. phreeq-unraid-diagnostics-20240421-0854.zip

I'm getting invalid option f

It all started with a drive failure. I had a drive fail, so I replaced it and rebuilt onto a new, bigger, drive. Once the rebuild was finished, somehow all of my docker containers were gone. Now, when I reinstall the container, and try to restore from app data backups, sometimes my GUI will go completely white, not even the menu bar is left. tower-diagnostics-20240420-1025.zip

Just a note if anyone runs into the problem I just had. I'm using postgresql for my database and when I updated the wikijs docker yesterday it broke. I didn't make a full note of the error I was getting, but part of it was ENOTFOUND undefined:undefined. Following instructions I can't find anymore for setting it up originally, my db section of the config.yml read: db: type: postgres # PostgreSQL / MySQL / MariaDB / MS SQL Server only: host: Postgres12.5 port: 5432 user: root pass: root db: wikijs ssl: false This was working for quite a while for me, but all of a sudden it didn't. I found that changing the host from the hostname of the postgres docker to the IP address fixed it for me.

Thanks for this, not sure if I just missed it when I tried it, or if it didn't work for me then. I'll give it another go in a little bit to see if I screwed up, which is ALWAYS possible. EDIT: Okay, the answer is I screwed up. I just tried it again and it did work. The only thing I can think of is, I was trying to use it behind SWAG and maybe I couldn't register the first account when processing through SWAG, but this time I did it from the local IP of my server. I set up the first account, then tested accessing through SWAG, and I was able to log in and all looks good. Now, I just need to dig in and figure out how to use the system. Thanks @Marzel!

No, and I gave up on not getting anywhere with it so I uninstalled the docker

@Shane Israel Okay, I switched over to the develop image; so far, so good. I'll check over the next couple of days to make sure that it stays running. Thanks!

I've run into a problem with this docker. It crashed on me at some point and now when I try to start it, it immediately stops and I get this in the logs: rm: cannot remove '/jobs.sqlite': Permission denied 2022-08-21 17:17:57,558 INFO __init__.update_config:26 | Validating configuration file... INFO [alembic.runtime.migration] Context impl SQLiteImpl. INFO [alembic.runtime.migration] Will assume non-transactional DDL. 2022-08-21 17:17:58,398 INFO __init__.update_config:26 | Validating configuration file... 2022-08-21 17:17:58,481 INFO schedule.init_schedule:17 | Initializing scheduled video scan. minutes=5 /usr/local/lib/python3.9/site-packages/apscheduler/util.py:94: PytzUsageWarning: The zone attribute is specific to pytz's interface; please migrate to a new time zone provider. For more details on how to do so, see https://pytz-deprecation-shim.readthedocs.io/en/latest/migration.html if obj.zone == 'local': /usr/local/lib/python3.9/site-packages/apscheduler/triggers/interval.py:66: PytzUsageWarning: The normalize method is no longer necessary, as this time zone supports the fold attribute (PEP 495). For more details on migrating to a PEP 495-compliant implementation, see https://pytz-deprecation-shim.readthedocs.io/en/latest/migration.html return self.timezone.normalize(next_fire_time) Traceback (most recent call last): File "/usr/local/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 1819, in _execute_context self.dialect.do_execute( File "/usr/local/lib/python3.9/site-packages/sqlalchemy/engine/default.py", line 732, in do_execute cursor.execute(statement, parameters) sqlite3.IntegrityError: UNIQUE constraint failed: apscheduler_jobs.id The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/local/lib/python3.9/site-packages/apscheduler/jobstores/sqlalchemy.py", line 98, in add_job self.engine.execute(insert) File "<string>", line 2, in execute File "/usr/local/lib/python3.9/site-packages/sqlalchemy/util/deprecations.py", line 401, in warned return fn(*args, **kwargs) File "/usr/local/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 3176, in execute return connection.execute(statement, *multiparams, **params) File "/usr/local/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 1306, in execute return meth(self, multiparams, params, _EMPTY_EXECUTION_OPTS) File "/usr/local/lib/python3.9/site-packages/sqlalchemy/sql/elements.py", line 325, in _execute_on_connection return connection._execute_clauseelement( File "/usr/local/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 1498, in _execute_clauseelement ret = self._execute_context( File "/usr/local/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 1862, in _execute_context self._handle_dbapi_exception( File "/usr/local/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 2043, in _handle_dbapi_exception util.raise_( File "/usr/local/lib/python3.9/site-packages/sqlalchemy/util/compat.py", line 207, in raise_ raise exception File "/usr/local/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 1819, in _execute_context self.dialect.do_execute( File "/usr/local/lib/python3.9/site-packages/sqlalchemy/engine/default.py", line 732, in do_execute cursor.execute(statement, parameters) sqlalchemy.exc.IntegrityError: (sqlite3.IntegrityError) UNIQUE constraint failed: apscheduler_jobs.id [SQL: INSERT INTO apscheduler_jobs (id, next_run_time, job_state) VALUES (?, ?, ?)] [parameters: ('fireshare_scan', 1661120578.617649, <memory at 0x150cb439cd00>)] (Background on this error at: https://sqlalche.me/e/14/gkpj) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/bin/gunicorn", line 8, in <module> sys.exit(run()) File "/usr/local/lib/python3.9/site-packages/gunicorn/app/wsgiapp.py", line 67, in run WSGIApplication("%(prog)s [OPTIONS] [APP_MODULE]").run() File "/usr/local/lib/python3.9/site-packages/gunicorn/app/base.py", line 231, in run super().run() File "/usr/local/lib/python3.9/site-packages/gunicorn/app/base.py", line 72, in run Arbiter(self).run() File "/usr/local/lib/python3.9/site-packages/gunicorn/arbiter.py", line 58, in __init__ self.setup(app) File "/usr/local/lib/python3.9/site-packages/gunicorn/arbiter.py", line 118, in setup self.app.wsgi() File "/usr/local/lib/python3.9/site-packages/gunicorn/app/base.py", line 67, in wsgi self.callable = self.load() File "/usr/local/lib/python3.9/site-packages/gunicorn/app/wsgiapp.py", line 58, in load return self.load_wsgiapp() File "/usr/local/lib/python3.9/site-packages/gunicorn/app/wsgiapp.py", line 48, in load_wsgiapp return util.import_app(self.app_uri) File "/usr/local/lib/python3.9/site-packages/gunicorn/util.py", line 412, in import_app app = app(*args, **kwargs) File "/usr/local/lib/python3.9/site-packages/fireshare/__init__.py", line 123, in create_app init_schedule(app.config['SCHEDULED_JOBS_DATABASE_URI'], File "/usr/local/lib/python3.9/site-packages/fireshare/schedule.py", line 20, in init_schedule scheduler.start() File "/usr/local/lib/python3.9/site-packages/apscheduler/schedulers/background.py", line 33, in start BaseScheduler.start(self, *args, **kwargs) File "/usr/local/lib/python3.9/site-packages/apscheduler/schedulers/base.py", line 162, in start self._real_add_job(job, jobstore_alias, replace_existing) File "/usr/local/lib/python3.9/site-packages/apscheduler/schedulers/base.py", line 867, in _real_add_job store.add_job(job) File "/usr/local/lib/python3.9/site-packages/apscheduler/jobstores/sqlalchemy.py", line 100, in add_job raise ConflictingIdError(job.id) apscheduler.jobstores.base.ConflictingIdError: 'Job identifier (fireshare_scan) conflicts with an existing job' ------------------------------------- User uid: 99 User gid: 100 -------------------------------------

I just installed this and I can't seem to register an account. Is there something I missed?

Have anyone gotten this working behind SWAG? I've tried building a conf file for it but I haven't gotten one to work yet.

You're welcome, glad it worked for you Sent from my HD1905 using Tapatalk