search

shikanon / kubeflow-manifests

kubeflow国内一键安装文件
GNU General Public License v3.0
338 stars 117 forks source link

您未获授权，无法查看此网页。 #44

Open zdzd123123 opened 3 years ago

zdzd123123 commented 3 years ago

katib-mysql一直crashLoopBackoff 30000端口显示，您未获授权，无法查看此网页。 已经重新安装很多遍了。 想问一下，您的集群配置、k8s版本等信息是什么样的

shikanon commented 3 years ago

@zdzd123123 katib-mysql crashLoopBackoff 的原因是什么？可以 describe 看看，是 pvc 创建不成功还是？

zs69 commented 3 years ago

我也遇到同样的问题，30000端口显示，您未获授权，无法查看此网页。

zdzd123123 commented 3 years ago

@zdzd123123 katib-mysql crashLoopBackoff 的原因是什么？可以 describe 看看，是 pvc 创建不成功还是？

image

zdzd123123 commented 3 years ago

@zdzd123123 katib-mysql crashLoopBackoff 的原因是什么？可以 describe 看看，是 pvc 创建不成功还是？

log:

2021-07-19T07:59:45.604875Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.24' socket: '/var/run/mysqld/mysqld.sock' port: 3306 MySQL Community Server - GPL. 2021-07-19T08:01:51.462559Z 0 [ERROR] [MY-013622] [InnoDB] [FATAL] fsync() returned EIO, aborting. 2021-07-19T08:01:51.462630Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: ut0ut.cc:555 thread 140347499116288 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 08:01:51 UTC - mysqld got signal 6 ; Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x46000 /usr/sbin/mysqld(my_print_stacktrace(unsigned char const, unsigned long)+0x2e) [0x561d495e696e] /usr/sbin/mysqld(handle_fatal_signal+0x31b) [0x561d489a2e5b] /lib/x86_64-linux-gnu/libpthread.so.0(+0x12730) [0x7fa55a7f7730] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x10b) [0x7fa559ed47bb] /lib/x86_64-linux-gnu/libc.so.6(abort+0x121) [0x7fa559ebf535] /usr/sbin/mysqld(+0x359d893) [0x561d49aa8893] /usr/sbin/mysqld(ib::fatal::~fatal()+0xc5) [0x561d49aab905] /usr/sbin/mysqld(os_file_flush_func(int)+0x4c5) [0x561d499678e5] /usr/sbin/mysqld(Fil_shard::redo_space_flush()+0x4b2) [0x561d49769fd2] /usr/sbin/mysqld(Fil_shard::flush_file_redo()+0x42) [0x561d4976a202] /usr/sbin/mysqld(+0x3448708) [0x561d49953708] /usr/sbin/mysqld(log_flusher(log_t)+0x438) [0x561d49956ab8] /usr/sbin/mysqld(std::thread::_State_impl<std::thread::_Invoker<std::tuple<Runnable, void ()(log_t), log_t*> > >::_M_run()+0xa9) [0x561d4992cb89] /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0xbbb2f) [0x7fa55a2b8b2f] /lib/x86_64-linux-gnu/libpthread.so.0(+0x7fa3) [0x7fa55a7ecfa3] /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7fa559f964cf] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash.

GithubZhitao commented 1 year ago

尝试通过机器https://ip:30000 访问后恢复正常