Closed MosesMuiru closed 2 months ago
I will remove this issue if you don't update your description to provide the minimum required information:
{:ejabberd, "~> 24.7"} i am using it as a dependency in elixir application it's happens all the time when using the iex terminal and rest api for ejabberd There is no relevant messages ,
On Mon, 2 Sept 2024 at 11:40, badlop @.***> wrote:
I will remove this issue if you don't update your description to provide the minimum required information:
- what ejabberd version you are using,
- where did you download or how you installed it,
- what changes you did to the default configuration,
- if you can reproduce the problem easily 100% or it happens only randomly
- what is done in the server to provoke the problem
- are there any other relevant log messages? not only error messages, maybe informative messages related to the problem?
- is there any way to reproduce the problem in other machines? can you reproduce the problem in other machines? can anybody else provoke the problem, or it only happens in that machine?
— Reply to this email directly, view it on GitHub https://github.com/processone/ejabberd/issues/4274#issuecomment-2324157797, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWGP5D7Y6L7XT3O5QNVBKJ3ZUQQBLAVCNFSM6AAAAABNPZZZC2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRUGE2TONZZG4 . You are receiving this because you authored the thread.Message ID: @.***>
config file
hosts:
loglevel: info
ca_file: ./cacert.pem
certfiles:
port: 5222
ip: "::"
module: ejabberd_c2s
max_stanza_size: 262144
shaper: c2s_shaper
access: c2s
starttls_required: true
port: 5269
ip: "::"
module: ejabberd_s2s_in
max_stanza_size: 524288
shaper: s2s_shaper
port: 5280
ip: "::"
module: ejabberd_http
request_handlers:
/admin: ejabberd_web_admin
/.well-known/acme-challenge: ejabberd_acme
- port: 3478 ip: "::" transport: udp module: ejabberd_stun use_turn: true
# turn_ipv4_address: "203.0.113.3"
## The server's public IPv6 address:
# turn_ipv6_address: "2001:db8::3"
- port: 1883 ip: "::" module: mod_mqtt backlog: 1000
s2s_use_starttls: optional
acl: local: user_regexp: "" loopback: ip:
access_rules: local: allow: local c2s: deny: blocked allow: all announce: allow: admin configure: allow: admin muc_create: allow: local pubsub_createnode: allow: local trusted_network: allow: loopback
api_permissions: "console commands": from: ejabberd_ctl who: all what: "" "webadmin commands": from: ejabberd_web_admin who: admin what: "" "admin access": who: access: allow:
shaper: normal: rate: 3000 burst_size: 20000 fast: 100000
shaper_rules: max_user_sessions: 10 max_user_offline_messages: 5000: admin 100: all c2s_shaper: none: admin normal: all s2s_shaper: fast
modules: mod_adhoc: {} mod_admin_extra: {} mod_announce: access: announce mod_avatar: {} mod_blocking: {} mod_bosh: {} mod_caps: {} mod_carboncopy: {} mod_client_state: {} mod_configure: {} mod_disco: {} mod_fail2ban: {} mod_http_api: {} mod_http_upload: put_url: @.@:5443/upload custom_headers: "Access-Control-Allow-Origin": @.@" "Access-Control-Allow-Methods": "GET,HEAD,PUT,OPTIONS" "Access-Control-Allow-Headers": "Content-Type" mod_last: {} mod_mam:
## For small servers SQLite is a good fit and is very easy
## to configure. Uncomment this when you have SQL configured:
## db_type: sql
assume_mam_usage: true
default: always
mod_mqtt: {} mod_muc: access:
storage:bookmarks: access_model: whitelist mod_push: {} mod_push_keepalive: {} mod_register:
ip_access: trusted_network mod_roster: versioning: true mod_s2s_dialback: {} mod_shared_roster: {} mod_stream_mgmt: resend_on_timeout: if_offline mod_stun_disco: {} mod_vcard: {} mod_vcard_xupdate: {} mod_version: show_os: false ModPresenceDemo: {}
On Mon, 2 Sept 2024 at 11:48, Moses @.***> wrote:
{:ejabberd, "~> 24.7"} i am using it as a dependency in elixir application it's happens all the time when using the iex terminal and rest api for ejabberd There is no relevant messages ,
On Mon, 2 Sept 2024 at 11:40, badlop @.***> wrote:
I will remove this issue if you don't update your description to provide the minimum required information:
- what ejabberd version you are using,
- where did you download or how you installed it,
- what changes you did to the default configuration,
- if you can reproduce the problem easily 100% or it happens only randomly
- what is done in the server to provoke the problem
- are there any other relevant log messages? not only error messages, maybe informative messages related to the problem?
- is there any way to reproduce the problem in other machines? can you reproduce the problem in other machines? can anybody else provoke the problem, or it only happens in that machine?
— Reply to this email directly, view it on GitHub https://github.com/processone/ejabberd/issues/4274#issuecomment-2324157797, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWGP5D7Y6L7XT3O5QNVBKJ3ZUQQBLAVCNFSM6AAAAABNPZZZC2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRUGE2TONZZG4 . You are receiving this because you authored the thread.Message ID: @.***>
What function you are executing when this error is thrown? It looks like it tries to send message to process named 'none', so it' not that strange that there is no such process.
Yes, So I am passing the required arguments in the function, I am not the one passing the the process name. I tried set_presence using ejabberd rest api but the same happens.
Ok, so you are calling set_presence
command. You are seeing this error because session info that you passed to that command (user, server, resource) doesn't exist, Looks like we need to improve detection of that case in it.
Thank you,
I was using the wrong resource
here is a command to get the resource of the user might help someone.
:ejabberd_sm.get_user_resources(User
, Host)
(exit) exited in: :p1_server.call(:none, {:set_presence, {:presence, "", :available, "", {:jid, "user1", "localhost", "tka1", "user1", "localhost", "tka1"}, {:jid, "user1", "localhost", "", "user1", "localhost", ""}, :away, [{:text, "en", "BB"}], 7, [], %{}}}, 1000) (EXIT) no process: the process is not alive or there's no process currently associated with the given name, possibly because its application isn't started (p1_utils 1.0.26) /deps/p1_utils/src/p1_server.erl:210: :p1_server.call/3