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.

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

<*push> Error: service type not selected, but service type IS defined #178

Open
DangerDane opened this issue Sep 24, 2015 · 3 comments
Open

Comments

@DangerDane
Copy link

I am getting the following error: '<*push> Error: service type not selected' when Push triggers, but the push goes through without a single hitch. The error wasn't present when I was running the Python version

@Mikaela
Copy link

Mikaela commented Sep 24, 2015

I am quite sure that you have loaded the module on both user and network levels. The Python version is only user level.

@dmd
Copy link

dmd commented Sep 18, 2019

I'm getting this as well. What's the fix? Pushes work but every single time I get "service type not selected".

@Strykar
Copy link

Strykar commented Jan 23, 2020

@dmd Do /msg *status unloadmod --type=network push. Do this for each IRC network it is loaded for.
/msg *status listmods should show you where you mistakenly loaded it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants