Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Pulsar Manager Error 404 - Missing CSRF Token #390

Closed
olsenpabu opened this issue Aug 30, 2023 · 6 comments
Closed

Pulsar Manager Error 404 - Missing CSRF Token #390

olsenpabu opened this issue Aug 30, 2023 · 6 comments

Comments

@olsenpabu
Copy link

Describe the bug
Using Helm chart to deploy pulsar manager. All pods are up and running. When accessing pulsar manager it throws missing CSRF Token.
To Reproduce
Steps to reproduce the behavior:

  1. Used Helm Package to deploy pulsar in Kubernetes setup
  2. Configured values.yaml to have a superuser to access the pulsar manager
  3. Accessed pulsar manager
    Observation: Error 404 - Missing CSRF Token shows in logs. Tried to login, also shows Error 404.

Expected behavior
Able to login and access pulsar manager.

Screenshots
image

Desktop (please complete the following information):

  • OS: macOS

Additional context
Same issue in local and AWS
@timoangerer
Copy link

I can confirm this issue on my end. I've followed the getting started guide and get the same error.

@willzhang
Copy link

willzhang commented Nov 27, 2023 •
edited
Loading

same here with pulsar v2.10.2

# kubectl -n pulsar logs -f pulsar-pulsar-manager-6db8ccb964-2sk5v  
Starting PostGreSQL Server
Adding group `pulsar' (GID 1000) ...
Done.
Adding user `pulsar' ...
Adding new user `pulsar' (1000) with group `pulsar' ...
Creating home directory `/home/pulsar' ...
Copying files from `/etc/skel' ...
Changing the user information for pulsar
Enter the new value, or press ENTER for the default
Use of uninitialized value $answer in chop at /usr/sbin/adduser line 582.
Use of uninitialized value $answer in pattern match (m//) at /usr/sbin/adduser line 583.
/pulsar-manager/startup.sh: 21: initdb: not found
/pulsar-manager/startup.sh: 22: pg_ctl: not found
createdb: error: could not connect to database template1: could not connect to server: No such file or directory
        Is the server running locally and accepting
        connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
psql: error: could not connect to server: No such file or directory
        Is the server running locally and accepting
        connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
        Full Name []:   Room Number []:         Work Phone []:  Home Phone []:  Other []: Is the information correct? [Y/n] Starting Pulsar Manager Front end
Starting Pulsar Manager Back end
Start servie no enable JWT.
2023-11-27 07:52:25,422 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.
2023-11-27 07:52:25,424 INFO supervisord started with pid 64
2023-11-27 07:52:26,426 INFO spawned: 'pulsar-manager-backend' with pid 65
2023-11-27 07:52:28,406 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 07:52:50,035 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 07:52:51,038 INFO spawned: 'pulsar-manager-backend' with pid 124
2023-11-27 07:52:52,152 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 07:53:09,252 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 07:53:10,256 INFO spawned: 'pulsar-manager-backend' with pid 183
2023-11-27 07:53:11,478 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 07:53:29,241 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 07:53:30,245 INFO spawned: 'pulsar-manager-backend' with pid 243
2023-11-27 07:53:31,413 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 07:53:49,962 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 07:53:50,965 INFO spawned: 'pulsar-manager-backend' with pid 302
2023-11-27 07:53:52,122 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 07:54:08,442 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 07:54:09,445 INFO spawned: 'pulsar-manager-backend' with pid 362
2023-11-27 07:54:10,638 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 07:54:25,374 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 07:54:26,377 INFO spawned: 'pulsar-manager-backend' with pid 421
2023-11-27 07:54:27,499 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 07:54:42,118 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 07:54:43,122 INFO spawned: 'pulsar-manager-backend' with pid 481
2023-11-27 07:54:44,357 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 07:55:00,113 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 07:55:01,117 INFO spawned: 'pulsar-manager-backend' with pid 540
2023-11-27 07:55:02,416 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 07:55:17,197 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 07:55:18,200 INFO spawned: 'pulsar-manager-backend' with pid 600
2023-11-27 07:55:19,307 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 07:55:33,637 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 07:55:34,641 INFO spawned: 'pulsar-manager-backend' with pid 659
2023-11-27 07:55:35,878 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 07:55:51,960 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 07:55:52,962 INFO spawned: 'pulsar-manager-backend' with pid 719
2023-11-27 07:55:54,133 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 07:56:09,942 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 07:56:10,945 INFO spawned: 'pulsar-manager-backend' with pid 778
2023-11-27 07:56:12,069 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 07:56:26,810 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 07:56:27,816 INFO spawned: 'pulsar-manager-backend' with pid 838
2023-11-27 07:56:29,078 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 07:56:44,931 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 07:56:45,934 INFO spawned: 'pulsar-manager-backend' with pid 897
2023-11-27 07:56:47,119 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 07:57:04,201 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 07:57:05,204 INFO spawned: 'pulsar-manager-backend' with pid 957
2023-11-27 07:57:06,348 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 07:57:20,965 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 07:57:21,968 INFO spawned: 'pulsar-manager-backend' with pid 1016
2023-11-27 07:57:23,208 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 07:57:39,005 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 07:57:40,008 INFO spawned: 'pulsar-manager-backend' with pid 1075
2023-11-27 07:57:41,187 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 07:57:56,102 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 07:57:57,106 INFO spawned: 'pulsar-manager-backend' with pid 1135
2023-11-27 07:57:58,260 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 07:58:14,217 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 07:58:15,220 INFO spawned: 'pulsar-manager-backend' with pid 1194
2023-11-27 07:58:16,364 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 07:58:31,043 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 07:58:32,048 INFO spawned: 'pulsar-manager-backend' with pid 1254
2023-11-27 07:58:33,212 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 07:58:48,817 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 07:58:49,821 INFO spawned: 'pulsar-manager-backend' with pid 1313
2023-11-27 07:58:50,941 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 07:59:07,373 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 07:59:08,377 INFO spawned: 'pulsar-manager-backend' with pid 1373
2023-11-27 07:59:09,512 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 07:59:25,272 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 07:59:26,274 INFO spawned: 'pulsar-manager-backend' with pid 1432
2023-11-27 07:59:27,432 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 07:59:43,072 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 07:59:44,077 INFO spawned: 'pulsar-manager-backend' with pid 1492
2023-11-27 07:59:45,201 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 08:00:01,258 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 08:00:02,264 INFO spawned: 'pulsar-manager-backend' with pid 1551
2023-11-27 08:00:03,414 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 08:00:18,147 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 08:00:19,150 INFO spawned: 'pulsar-manager-backend' with pid 1611
2023-11-27 08:00:20,300 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 08:00:35,977 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 08:00:36,983 INFO spawned: 'pulsar-manager-backend' with pid 1670
2023-11-27 08:00:38,131 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 08:00:52,840 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 08:00:53,842 INFO spawned: 'pulsar-manager-backend' with pid 1730
2023-11-27 08:00:55,138 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 08:01:12,255 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 08:01:13,261 INFO spawned: 'pulsar-manager-backend' with pid 1789
2023-11-27 08:01:14,532 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 08:01:30,553 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 08:01:31,557 INFO spawned: 'pulsar-manager-backend' with pid 1849
2023-11-27 08:01:32,741 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 08:01:48,426 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 08:01:49,430 INFO spawned: 'pulsar-manager-backend' with pid 1908
2023-11-27 08:01:50,643 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 08:02:04,217 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 08:02:05,220 INFO spawned: 'pulsar-manager-backend' with pid 1968
2023-11-27 08:02:06,344 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 08:02:22,047 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 08:02:23,050 INFO spawned: 'pulsar-manager-backend' with pid 2027
2023-11-27 08:02:24,195 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 08:02:39,129 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 08:02:40,133 INFO spawned: 'pulsar-manager-backend' with pid 2086
2023-11-27 08:02:41,317 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 08:02:56,066 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 08:02:57,069 INFO spawned: 'pulsar-manager-backend' with pid 2146
2023-11-27 08:02:58,356 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 08:03:12,964 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 08:03:13,969 INFO spawned: 'pulsar-manager-backend' with pid 2205
2023-11-27 08:03:15,101 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 08:03:30,230 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 08:03:31,234 INFO spawned: 'pulsar-manager-backend' with pid 2265
2023-11-27 08:03:32,367 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 08:03:47,102 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 08:03:48,105 INFO spawned: 'pulsar-manager-backend' with pid 2324
2023-11-27 08:03:49,232 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 08:04:04,032 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 08:04:05,035 INFO spawned: 'pulsar-manager-backend' with pid 2384
2023-11-27 08:04:06,189 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 08:04:21,052 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 08:04:22,056 INFO spawned: 'pulsar-manager-backend' with pid 2443
2023-11-27 08:04:23,324 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 08:04:38,021 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 08:04:39,024 INFO spawned: 'pulsar-manager-backend' with pid 2503
2023-11-27 08:04:40,157 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 08:04:55,804 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 08:04:56,810 INFO spawned: 'pulsar-manager-backend' with pid 2562
2023-11-27 08:04:58,238 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-11-27 08:05:13,850 INFO exited: pulsar-manager-backend (exit status 1; not expected)
2023-11-27 08:05:14,853 INFO spawned: 'pulsar-manager-backend' with pid 2622

@zhixiangjoy
Copy link

same problem!

@alpreu
Copy link

alpreu commented Dec 29, 2023 •
edited
Loading

You can try @streamvisor as an enterprise-grade alternative to pulsar-manager. It's free :)

@lhotari
Copy link
Member

lhotari commented Feb 14, 2024

You can try @streamvisor as an enterprise-grade alternative to pulsar-manager. It's free :)

@alpreu Please remove your advertisements from all Apache Pulsar repositories.

@lhotari
Copy link
Member

lhotari commented Feb 15, 2024

#457 improves pulsar manager integration. Closing this issue.

@lhotari lhotari closed this as completed Feb 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@lhotari @alpreu @zhixiangjoy @timoangerer @willzhang @olsenpabu