Saltar al contenido principal

Búsqueda

Búsqueda

High Cpu With Bartender 10.0

Comentarios

3 comentarios

  • Avatar
    Legacy Poster
    I can reproduce this behavior with every print job triggered. Equal if trigger is File or TCP/IP and if it's 1 or 3 parallel prints. Find attached a screenshot of History Explorer where we can see that it has a lot of license requests (and they are accepted) also only one print job was triggered during this time. It produces thousand of same message during this short time, which seems to be the root cause of the problem.
    0
  • Avatar
    Susan Chen
    Moderador
    Hi, Markus:


    1) Do you use 8 core CPU as server? There's not a lot of benefit to running more processes than you have cores.

    2) Can you translate the message you get to English if possible? Can you turn on Bartender and commander log as well through Administer-> Log etup -> Text File Log-> tick "Log Message" ?

    3) Can you send your commander *.tl file and trigger file samples and the steps to asiatech@seagullscientific.com, we can try on our Window 2003 environment to compare with your result?


    Thanks!
    0
  • Avatar
    Legacy Poster
    [quote name='Susan C - Seagull Support' timestamp='1331653588' post='1979']
    Hi, Markus:


    1) Do you use 8 core CPU as server? There's not a lot of benefit to running more processes than you have cores.

    2) Can you translate the message you get to English if possible? Can you turn on Bartender and commander log as well through Administer-> Log etup -> Text File Log-> tick "Log Message" ?

    3) Can you send your commander *.tl file and trigger file samples and the steps to asiatech@seagullscientific.com, we can try on our Window 2003 environment to compare with your result?


    Thanks!
    [/quote]

    Unfortunately I had to deinstall version 10.0 because of the problems (it's one of our productive servers) and reinstalled version 9.3 which we had installed before and which works with same configuration without these problems.

    1) We have only 1 core CPU in VM configured, but problem could also be reproduced if only one print job was triggered.
    2) The message translated: Bartender has requested authorization for printing from License Server. The Seagull License Server has approved the request.

    The other SLS connected Bartender installations with 9.3 still worked without problems, so it seems a problem with SLS 10.0 in connection with Bartender 10.0 (in our environment).
    Unfortunately I do not have time (and a second license) to install a seperate 10.0 installation for further investigation.
    0

Iniciar sesión para dejar un comentario.