https://signoz.io logo
#support
Title
# support
m

Mark Raynsford

10/14/2022, 6:15 PM
hello! i wiped my installation from last week, cloned commit
5eed384ffe05fd734bbbd8ae80b921106c505149
(the current
main
) and ran the usual
docker-compose -f docker/clickhouse-setup/docker-compose.yaml up -d
command to set up a fresh signoz. for whatever reason, i'm now unable to get into the UI (there are no existing accounts, i'm trying to create a new account):
p

Pranay

10/14/2022, 6:47 PM
@Mark Raynsford What was the version number - for the scenario when this method worked for you?
Also, can you confirm if the version you are running is same as the latest release?
m

Mark Raynsford

10/14/2022, 7:06 PM
it seems that i was previously using
cc3f36b62bd0466ed5627505d0ea9a6c0d0e258f
, which was the head of the
develop
branch on 2022-09-22. i'm now using
5eed384ffe05fd734bbbd8ae80b921106c505149
which is one commit newer than the
0.11.2
release tag (the diff between the two commits appears to be empty)
p

Prashant Shahi

10/15/2022, 1:49 PM
@Mark Raynsford it is likely that clickhouse and sqlite data are not properly clean. Those volume data are mapped to local directory in
data/clickhouse
and
data/signoz
folders.
you can either use previous admin credentials to Login or clean up those data folders.
@Ankit Nayan @Palash Gupta we should update information box in signup UI to show appropriate message.
m

Mark Raynsford

10/15/2022, 2:35 PM
ah, thanks! i didn't realize there was any data that outlived the containers there. i'll give it a try shortly
just to confirm: that was the problem. the old
data
directory was hanging around. i agree the error message could be better
thanks for the assistance!