Run Loading Job Error - Tigergraph Enterprise Free Edition - Help Please

1

I had a Loading Job that was successfully loading before and it started failing with a very cryptic message in the log file - I restarted the server but still getting the same error - The gadmin status shows all the services are running - I am adding the issues I saw in the log file - I can attach the log file if needed

##1----------

====================================

Cannot bind to ipc:///var/tmp/tigergraph/tigergraph/gsql_3383768 StatusHubAgentServer won’t start

WARNING: Logging before InitGoogleLogging() is written to STDERR

I0323 16:29:00.729091 3383768 config.cpp:192] Queue infos:

I0323 16:29:00.729135 3383768 config.cpp:194] queue name:GSE_journal_0 topic:Topic: GSE_journal_0

source: GSE

target: GSE

##2----------
W0323 16:29:00.783666 3383768 heartbeat_client.cpp:465] CLIENT: Detect server update, old server: , new server: 127.0.0.1:17797. Tried to start client ses

sion, session: 0x2f54328 state:CLIENT_SESSION_ISSUED rc: kOk

I0323 16:29:00.783715 3383812 heartbeat_client.cpp:339] ClientSession is issued. Session 0x2f54328 Server:127.0.0.1:17797

I0323 16:29:00.784287 3383816 single_thread_worker.cpp:83] SingleThreadWorker start: HeartbeatClient

I0323 16:29:00.784325 3383816 client_watcher_manager.cpp:32] Reconnect session, re-watch all paths. size:0

I0323 16:29:00.793799 3383768 gdict.cpp:343] Dictionary initialize succeed, took 64 milliseconds

E0323 16:29:00.816177 3383768 gconfig_general.cpp:320] Graph SalesJourney failed to get end points. List endpoints files failed. rc:kNotFound

E0323 16:29:00.862646 3383768 gconfig_general.cpp:320] Graph SalesJourney failed to get end points. List endpoints files failed. rc:kNotFound

##3----

16:29:00.865062 gtimer.cpp:82] MessageQueue|Kafka|CreateWriter|loading-logLog folder at /app1/tigergraph/log/fileLoader

ENTERPRISE_EDITION

F0323 16:29:00.870641 3383768 zeromq.cpp:189] Check failed: false id_responseQ_QUERY_RESTPP-LOADER_1Q,tcp://:8501, error no:98, strerr:Address already in*

use

**** Check failure stack trace: ****

##4 — ------

E0323 16:29:00.893316 3383768 glogging.cpp:132] ============ Crashed with stacktrace ============

0# FailureSignalHandler at /home/graphsql/product/src/engine/utility/gutil/glogging.cpp:132

1# 0x00007F3C933DBC20 in /app1/tigergraph/app/3.4.0/.syspre/usr/lib_ld1/libpthread.so.0

2# 0x00007F3C9239037F in /app1/tigergraph/app/3.4.0/.syspre/usr/lib_ld1/libc.so.6

3# 0x00007F3C9237ADB5 in /app1/tigergraph/app/3.4.0/.syspre/usr/lib_ld1/libc.so.6

4# DumpStackTraceAndExit at src/utilities.cc:151

5# 0x000000000175915A at src/logging.cc:1536

6# google::LogMessage::SendToLog() at src/logging.cc:1493

7# google::LogMessage::Flush() at src/logging.cc:1363

8# google::LogMessageFatal::~LogMessageFatal() at src/logging.cc:2113

9# gnet::ZeroMQBase::CheckError(std::string&, std::string&) at /home/graphsql/product/src/engine/utility/gnet/zeromq/zeromq.cpp:188

10# gnet::ZeroMQReader::ZeroMQReader(std::string, void, gnet::ZeroMQMode, std::vector<std::string, std::allocatorstd::string >) at /home/graphsql/produ*

ct/src/engine/utility/gnet/zeromq/zeromq.cpp:504

11# gnet::ZeroMQFactory::getQueueMsgReader(std::string, unsigned long) at /home/graphsql/product/src/engine/utility/gnet/zeromq/zeromqfactory.cpp:92

12# gnet::GSQLMessageQueueFactory::getQueueMsgReader(std::string, unsigned long) at /home/graphsql/product/src/engine/utility/gnet/gsqlmessagequeuefactory

.cpp:116

13# gnet::QueueReadHelper::QueueReadHelper(gnet::MessageQueueFactory, std::string) at /home/graphsql/product/src/engine/utility/gnet/queuereadhelper.cpp:*

35

14# postservice::IdConverter::RegisterEnumIDSReader() at /home/graphsql/product/src/engine/core/topology/postservice/idconverter.cpp:77

15# restpp::factory::Init(std::string const&, std::string const&, unsigned int, unsigned int, bool) at /home/graphsql/product/src/engine/realtime/restpp/f

actory/factory.cpp:170

16# StartService(int, char*) at /home/graphsql/product/src/engine/realtime/restpp/ensemble/loader/loaderworker.cpp:152*

17# main at /home/graphsql/product/src/engine/realtime/restpp/ensemble/loader/loaderworker.cpp:365

18# 0x00007F3C9237C493 in /app1/tigergraph/app/3.4.0/.syspre/usr/lib_ld1/libc.so.6

19# 0x0000000000452F71 in /app1/tigergraph/app/3.4.0/bin//tg_app_fileldr

============ End of stacktrace ============

**** Aborted at 1648070941 (unix time) try “date -d @1648070941” if you are using GNU date ****

Any help?

Thanks,

2

——

Hi @ramaiah78

Im new to Tigergraph but I have seen similar messages in other products I have worked with.

The error message cannot bind usually means the port is being used by another process.

—-

ENTERPRISE_EDITION

F0323 16:29:00.870641 3383768 zeromq.cpp:189] Check failed: false id_responseQ_QUERY_RESTPP-LOADER_1Q,tcp://:8501, error no:98, strerr:Address already in*

use

—-

Are you positive you didn’t change or make any server updates to the ports from a server reboot?

Please attach the full log file.

I’ll let the @TigerGraph team respond further if this is more detailed oriented response.

Cheers

Anil :tiger:

2 Likes
3

Thanks Anil - I didnt perform any server update to the ports , except that i installed the ML Workbench on the server Dont know whether that installation clash with the ports

How to attach a file here - i dont see any option Looks like only images can be uploaded here

Thanks

4

Hi Ramaiah

As per the documentation it says it uses port 8000.

Prerequisites

  • TigerGraph ML Workbench is installed on your machine.
  • A running TigerGraph instance with port 8000 accessible by the server running the ML Workbench. For a TigerGraph cluster, only the port 8000 on the m1 machine needs to be accessible.

Try running

$cat /etc/services on your Linux machine.

And see if any other service is using the tigergraph or ml workbench port.

Also regarding uploading of files.

When you respond. There is a link icon to the top and it should allow you to upload files.

Hope this helps.

Cheers
Anil :tiger:

2 Likes
5

Thanks Anil - I rebooted the linux server and the error disappeared and I could able to run the job - Weird.

2 Likes
6

Thanks @anilm for helping others in the community!

1 Like