[Blocker] my local Docker installation stopped working #286
Comments
|
Browsing through the Docker consoles revealed |
|
I do not know what the error message shown above means - but it does not seem to be relevant for my problem. I simply tried again, stopped the Docker container completely and restarted it again - and now it seems to work. It might have been a race condition or s.th. similar. Sorry for bothering you! |
|
Today, I ran into the same situation again...my browser logged the following error messages It happened after the system logged me out (with a session expiration warning) but did not let me log in again (pressing the "Ok" button of the message box simply showed the same error message again) Unfortunately, closing the browser window and restarting Docker did not help yet today... The only detail I know so far is that I should start over as soon as the docker logs shows multiple lines containing This seems to be the polite version of "hey, I crashed, start over again!" |
|
Hi,
are there any other logs? Usually the only thing that could prevent the
system from rebooting is a corrupted Mongo db.
…On Thu, Apr 4, 2024 at 5:36 PM Andreas Rozek ***@***.***> wrote:
Today, I ran into the same situation again...my browser logged the
following error messages
WebSocketService.js:15 WebSocket connection to 'ws://127.0.0.1:8086/?app=660ec1aede3a5f1715866c86&jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJyb2xlIjoidXNlciIsImlzcyI6Ik1BVEMiLCJpZCI6IjY1ZmM5MjQ1N2Q1YjlkMTQ1NDk3OGU0ZCIsImV4cCI6MTcxMjI5Mzc3NSwiZW1haWwiOiJhLXJvemVrQG1haWwuZGUifQ.IsA6Sl7bJ2YWteg-0kpXaDnOu3YIEWQMw6O1hjTFihU' failed:
init @ WebSocketService.js:15
Logger.js:21 WebSocketService.init() > cannot init Event
error @ Logger.js:21
It happened after the system logged me out (with a session expiration
warning) but did not let me log in again (pressing the "Ok" button of the
message box simply showed the same error message again)
Unfortunately, closing the browser window and restarting Docker did not
help yet today...
—
Reply to this email directly, view it on GitHub
<#286 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABWHOQAV6EFM3RGP5E5TJCDY3VXQ5AVCNFSM6AAAAABFU7MTZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZXGU2DCNJRHA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
“Overfitting” is not about an excessive amount of physical exercise...
|
|
Ok, I'll give up for today. Perhaps, the following log entries can help you: |
|
which logs do you want? |
|
here is an excerpt from the MondoDB container log |
|
and here is an excerpt from the quant-ux-websocket-server Surprisingly, however, i am logged in! |
|
Here are the logs from a fresh Docker start (after clearing all terminals) quant-ux-mongo quant-ux-backend quant-ux-websocket-server quant-ux-frontend |
|
as you can see, it already starts with "Check Connections 0"...no chance for me I'll give up for today and see if it will work tomorrow - otherwise, I'll give up completely. |
|
Hi,
the tokens time out after 7 days. They are stored in the browser in local
storage, and should be deleted on logout, or when the popup shows up.
Could you try to use an incognito browser, or delete the local storage for
the server?
…On Thu, Apr 4, 2024 at 5:52 PM Andreas Rozek ***@***.***> wrote:
and here is an excerpt from the quant-ux-websocket-server
2024-04-04 17:39:28 2024-04-04T15:39:28.137Z Check Connections 0
2024-04-04 17:39:56 2024-04-04T15:39:56.274Z authenticate() > User not allowed to access 660ec1aede3a5f1715866c86
2024-04-04 17:39:56 2024-04-04T15:39:56.277Z Cannot autheicate request
Surprisingly, however, i *am* logged in!
—
Reply to this email directly, view it on GitHub
<#286 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABWHOQBCKXF7BCA2JPHEVRDY3VZNXAVCNFSM6AAAAABFU7MTZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZXGU4DEMZVHA>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
“Overfitting” is not about an excessive amount of physical exercise...
|
|
7 days? I get logged out much more often. What do you mean with "localstorage" for the server? and what will I loose if I do that? |
|
there is a "quxuser" entry in my browser's "localstorage" - do you mean that? |
|
"Check Connections 0" comes from the web socket server, which is only used
for collaborative working. Having a zero in there is fine.
…On Thu, Apr 4, 2024 at 6:00 PM Andreas Rozek ***@***.***> wrote:
as you can see, it already starts with "Check Connections 0"...no chance
for me
I'll give up for today and see if it will work tomorrow - otherwise, I'll
give up completely.
—
Reply to this email directly, view it on GitHub
<#286 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABWHOQESLYGSQ4XIWHA77Q3Y3V2KBAVCNFSM6AAAAABFU7MTZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZXGYYDMMZRGY>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
“Overfitting” is not about an excessive amount of physical exercise...
|
|
localstorage is in the browser. It's like a better cookie.
…On Thu, Apr 4, 2024 at 6:02 PM Andreas Rozek ***@***.***> wrote:
7 days? I get logged out much more often.
What do you mean with "localstorage" for the server? and what will I loose
if I do that?
—
Reply to this email directly, view it on GitHub
<#286 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABWHOQFLPKZMADBLAX3TOQ3Y3V2PXAVCNFSM6AAAAABFU7MTZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZXGYYTCMRXGQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
“Overfitting” is not about an excessive amount of physical exercise...
|
|
yes
…On Thu, Apr 4, 2024 at 6:03 PM Andreas Rozek ***@***.***> wrote:
there is a "quxuser" entry in my browser's "localstorage" - do you mean
that?
—
Reply to this email directly, view it on GitHub
<#286 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABWHOQDKNZOTZKYLNDPOIYLY3V2WNAVCNFSM6AAAAABFU7MTZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZXGYYTIOJYHA>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
“Overfitting” is not about an excessive amount of physical exercise...
|
|
ok, I'll delete that - stand by |
|
Yep, that worked - thank you very much! So the "cookie" broke somehow? nevertheless, family is calling - I'll have to leave now. Thanks a lot for your immediate help! |
|
This is weird, I will still take a look.
Also, I merged the new UI into master. In some minutes there should be a
new Dockerimage for the front end.
…On Thu, Apr 4, 2024 at 6:08 PM Andreas Rozek ***@***.***> wrote:
Yep, that worked - thank you very much! So the "cookie" broke somehow?
nevertheless, family is calling - I'll have to leave now.
Thanks a lot for your immediate help!
—
Reply to this email directly, view it on GitHub
<#286 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABWHOQGRJNO36FZP4AXOT7LY3V3JHAVCNFSM6AAAAABFU7MTZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZXGYZDOOJSG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
“Overfitting” is not about an excessive amount of physical exercise...
|
|
I just ran into a deadlock that stopped me working with QuantUX. The server logs showed many lines which may help you identifying the problem |
|
Personally, I think I'll have to give up evaluating QuantUX, as it (despite being an impressive piece of software) simply stops working to often - and I always have the fear of loosing the work I've done so far... |
|
Hi,
I am running basically the same setup for years and have nether experienced
such errors.
Can you share the system specs? Are you processing a lot of images
(uploads)?
Andreas Rozek ***@***.***> schrieb am Do., 11. Apr. 2024,
17:07:
… Personally, I think I'll have to give up evaluating QuantUX, as it
(despite being an impressive piece of software) simply stops working to
often - and I always have the fear of loosing the work I've done so far...
—
Reply to this email directly, view it on GitHub
<#286 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABWHOQGEFG3IPIIMSDGK6EDY42YK3AVCNFSM6AAAAABFU7MTZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJQGAZTQNBRG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
The basic specs of my system are:
I'm using two browser sessions:
The template already contains around 140 PNG icons (24x24) plus two PNGs for app backgrounds - nothing special. Until now, "App"s are built of up to 2 screens with 768x1024px (plus the template screen - because it is impossible to copy a widget from one browser session to the other). Again, nothing special - real apps are usually much larger. Since I normally have to stop and start the Docker container several times in order to get access to Quant-UX again, I assume some kind of nasty race condition between the three components (unfortunately, that would be the most ugly situation one can think of) |
|
Hi.
All of the server frameworks are using event loops and are thus more or
less single threaded. Also JS is single threaded, so would outline some
race conditions.
Still a very strange behaviour. This happens when you export as zip files?
The errors indicate that the images could not be loaded. Did they show up
in the canvas?
Andreas Rozek ***@***.***> schrieb am Fr., 12. Apr. 2024,
03:22:
… The basic specs of my system are:
- Apple Mac mini M1 with 16GB RAM running macOS Ventura 13.6.1
- Docker Desktop 4.25.1 with Engine 24.0.6
- running Quant-UX in a container as described on your GitHub page
I'm using two browser sessions:
- a first one for a (growing) set of templates
- a second one for the actual design
The template already contains around 140 PNG icons (24x24) plus two PNGs
for app backgrounds - nothing special.
Until now, "App"s are built of up to 2 screens with 768x1024px (plus the
template screen - because it is impossible to copy a widget from one
browser session to the other). Again, nothing special - real apps are
usually much larger.
Since I normally have to stop and start the Docker container several times
in order to get access to Quant-UX again, I assume some kind of nasty race
condition between the three components (unfortunately, that would be the
most ugly situation one can think of)
—
Reply to this email directly, view it on GitHub
<#286 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABWHOQGCCS5IKXBOYIXXSZ3Y45AN5AVCNFSM6AAAAABFU7MTZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJQHA2DSMZWHA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
as far as I remember, the problem occurred when I tried to "Save As..." a project under a different name. And, yes, all icons did show up, although it took many seconds until all of them did. "Importing" my "Templates" project also took surprisingly long (perhaps as long as the icons needed to show up) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
That's a real blocker!
I was just trying Quant-UX again, using my local Docker installation (created according the docs) and, after a few hours of designing, switching from one prototype back to the overview hang up Quant-UX which got stuck in the "loading" screen.
I tried to reopen the browser window, restarted the browser, restarted the dock container - but nothing worked.
Instead, the server log file gets filled with lines showing
quant-ux-websocket-server | 2024-04-03T09:57:20.019Z Check Connections 0and the browser console says:
Now I'm stuck and I cannot access anything I did so far.
That's bad...
What can I do to get Quant-UX working again?
The text was updated successfully, but these errors were encountered: